| 3 | Approval of the Agenda | |
|---|---|---|
| R3-214600 | RAN3#114-e Meeting Agenda | RAN3 Chair |
| 4 | Approval of the minutes from previous meetings | |
| R3-214601 | RAN3#113-e Meeting report | ETSI-MCC |
| R3-214603 | RAN3#113-e Meeting report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-215105 | Guidelines for RAN3 Electronic Meetings | RAN3 Chairman, RAN3 Vice-Chairs |
| 6 | Organizational topics | |
| R3-215984 | Workload in RAN3 and in RAN | Ericsson, Qualcomm Incorporated, InterDigital, NTT DOCOMO Inc., AT&T |
| 7 | General, protocol principles and issues | |
| R3-214602 | TR 30.531 v1.40.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| 8.1 | New Incoming LSs | |
| R3-214667 | Reply LS on establishment/resume cause value and UAC on L2 SL Relay | CT1 |
| R3-214668 | Reply LS on NAS-based busy indication | CT1 |
| R3-214669 | Reply LS on lower bound for eDRX cycle length | CT1 |
| R3-214670 | LS on extended NAS supervision timers at satellite access | CT1 |
| R3-214671 | LS on Guidelines on Port Allocation for New 3GPP Interfaces | CT4 |
| R3-214673 | Reply LS on determination of location estimates in local co-ordinates | RAN1 |
| R3-214674 | LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN2 | RAN1 |
| R3-214675 | LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN3 | RAN1 |
| R3-214676 | LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN4 | RAN1 |
| R3-214678 | LS on PRS measurement outside the measurement gap | RAN1 |
| R3-214679 | LS on beam/antenna information for DL AOD in NR positioning | RAN1 |
| R3-214683 | LS on the MBS broadcast service continuity and MBS session identification | RAN2 |
| R3-214684 | LS on UE Power Saving | RAN2 |
| R3-214685 | LS to RAN3 on the misalignment in SRS configuration | RAN2 |
| R3-214686 | Reply LS on determination of location estimates in local co-ordinates | RAN2 |
| R3-214687 | Reply LS to SA2 on scheduled location time | RAN2 |
| R3-214691 | Response LS on CHO with SCG configuration | RAN2 |
| R3-214692 | LS on paging for multicast session activation notification | RAN2 |
| R3-214695 | Reply LS on RACH report for SgNB and information needed for MRO in SCG Failure Report | RAN2 |
| R3-214702 | Reply LS on TCI state updates for L1/L2 centric inter-cell mobility | RAN4 |
| R3-214703 | Reply LS on support of PWS over SNPN | SA1 |
| R3-214705 | LS on Clarification of UE with CAG information in UE subscription | SA2 |
| R3-214707 | Reply LS on Network Switching for MUSIM | SA2 |
| R3-214709 | LS on the UE Radio Capability for Paging in RACS context | SA2 |
| R3-214710 | LS on latest progress and outstanding issues in SA WG2 | SA2 |
| R3-214711 | LS Reply on Supporting UP Integrity Protection Policy Handling for Interworking from 5GS to EPS | SA2 |
| R3-214713 | LS on full registration request message to be rerouted via RAN | SA3 |
| R3-214714 | LS on User Plane Integrity Protection for eUTRA connected to EPC | SA3 |
| R3-214715 | Reply to LS on support of PWS over SNPN | SA3 |
| R3-214718 | Reply LS on QoE configuration and reporting related issues | SA4 |
| R3-214719 | LS on PSCELL ID availability in SGW CDR | SA5 |
| R3-214721 | Reply LS on QoE configuration and reporting related issues | SA5 |
| R3-214723 | LS to RAN3 on the F1 interface for MOCN network sharing for multiple Cell Identity broadcast scenario | SA5 |
| R3-214743 | Discussion on CHO with SCG configuration | ZTE |
| R3-214744 | (TP for CPAC BLCR to TS36.423) Support CHO with SCG configuration | ZTE |
| R3-214745 | (TP for CPAC BLCR to TS38.423) Support CHO with SCG configuration | ZTE |
| R3-214746 | (TP for CPAC BLCR to TS37.340) Support CHO with SCG configuration | ZTE |
| R3-214750 | Discussion on MBS broadcast service continuity | ZTE |
| R3-214752 | [DRAFT] Reply LS on the MBS broadcast service continuity and MBS session identification | ZTE |
| R3-214753 | (TP for BL CR for 38.413) Multicast group paging | ZTE |
| R3-214754 | (TP for BL CR for 38.423) Multicast group paging | ZTE |
| R3-214755 | [DRAFT] Reply LS on paging for multicast session activation notification | ZTE |
| R3-214787 | (TP for 38.413) Stage 3 for MBS Group Paging | Nokia, Nokia Shanghai Bell |
| R3-214797 | Continuation of the work on CHO with SCG configuration | Nokia, Nokia Shanghai Bell |
| R3-214798 | Enabling CHO with SCG configuration | Nokia, Nokia Shanghai Bell |
| R3-214799 | Enabling CHO with SCG configuration | Nokia, Nokia Shanghai Bell |
| R3-214800 | Response LS on Conditional Handover with SCG configuration scenarios | Nokia, Nokia Shanghai Bell |
| R3-214885 | Enforcing CAG restrictions after inter-system handover | Qualcomm Incorporated |
| R3-214886 | Enforcing CAG restrictions after inter-system handover | Qualcomm Incorporated |
| R3-214887 | Handling of UE Security Capabilities | Qualcomm Incorporated |
| R3-214888 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated |
| R3-214889 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated |
| R3-214890 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated |
| R3-214891 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated |
| R3-214892 | [DRAFT] Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | Qualcomm Incorporated |
| R3-214922 | CHO with SCG configuration | Qualcomm Incorporated |
| R3-214967 | Feedback on TS 23.247 for NG-RAN dependencies | Nokia, Nokia Shanghai Bell |
| R3-214968 | Response LS on latest progress and outstanding issues in SA2 | Nokia, Nokia Shanghai Bell |
| R3-214969 | Response LS on paging for multicast session activation notification | Nokia, Nokia Shanghai Bell |
| R3-215024 | Discussion on RAN2 LS on Conditional Handover with SCG configuration scenarios | Huawei |
| R3-215025 | Support of CHO with SCG configuration | Huawei |
| R3-215026 | Support of CHO with SCG configuration | Huawei |
| R3-215027 | Support of CHO with SCG configuration | Huawei |
| R3-215028 | Support of CHO with SCG configuration | Huawei |
| R3-215029 | (TP for SON BLCR for TS 38.423): Discussion on RACH report for SgNB and information needed for MRO in SCG Failure Report | Huawei |
| R3-215041 | The MBS broadcast service continuity and MBS session identification | CATT |
| R3-215042 | Reply LS on the MBS broadcast service continuity and MBS session identification | CATT |
| R3-215049 | Discussion on the issue associated with SCG RA report in R2-2109208 | CATT |
| R3-215050 | (TP on SON for 36.423) TP on SCG RA report | CATT |
| R3-215051 | (TP on SON for 38.423) TP on SCG RA report | CATT |
| R3-215058 | [Draft] Reply LS on latest progress and outstanding issues in SA WG2 | CATT |
| R3-215061 | The MBS broadcast service continuity and MBS session identification | CATT |
| R3-215062 | Reply LS on the MBS broadcast service continuity and MBS session identification | CATT |
| R3-215077 | Discussion on L1/L2-Centric Inter-Cell Mobility in RAN3 in Rel 17 | Nokia, Nokia Shanghai Bell |
| R3-215085 | Support of CHO with SCG configuration | Huawei |
| R3-215086 | [Draft] Reply LS on RACH report for SgNB and information needed for MRO in SCG Failure Report | Huawei |
| R3-215091 | Further discussion on NAS-based busy indication | Huawei |
| R3-215173 | Clarification of UE with CAG information in UE subscription | Huawei |
| R3-215174 | [Draft] Reply LS on clarification of UE with CAG information in UE subscription | Huawei |
| R3-215175 | Clarification of UE with CAG information in UE subscription | Huawei |
| R3-215185 | On Network Sharing with multiple Cell-ID broadcast | Ericsson |
| R3-215186 | [DRAFT] Reply LS to "LS to RAN3 on the F1 interface for MOCN network sharing for multiple Cell Identity broadcast scenario" | Ericsson |
| R3-215187 | On the LS from SA2 on “Clarification of UE with CAG information in UE subscription” | Ericsson |
| R3-215188 | Enable PNI-NPN related access control at AMF at inter-system handover to NG-RAN | Ericsson |
| R3-215189 | Enable PNI-NPN related access control at AMF at inter-system handover to NG-RAN | Ericsson |
| R3-215190 | On the LS from SA2 to RAN on outstanding issues for NR/5G MBS | Ericsson |
| R3-215191 | [DRAFT] Reply LS on latest progress and outstanding issues in SA WG2 | Ericsson |
| R3-215192 | On RAN2 Group Paging Assumptions for NR MBS | Ericsson |
| R3-215193 | [DRAFT] Reply LS on paging for multicast session activation notification | Ericsson |
| R3-215194 | Discussion on RAN2 LS on the MBS broadcast service continuity and MBS session identification | Ericsson |
| R3-215195 | [DRAFT] Reply LS on the MBS broadcast service continuity and MBS session | Ericsson |
| R3-215217 | Reply LS on RACH report for SgNB and information needed for MRO in SCG Failure Report | Ericsson |
| R3-215218 | On delivering SN related RA reports to the SN | Ericsson |
| R3-215219 | (TP for SON BL CR for TS38.423-g70): TP for RACH report availability indication | Ericsson |
| R3-215220 | (TP for SON BL CR for TS38.473-g70): RACH report availability indication | Ericsson |
| R3-215221 | (TP for SON BL CR for TS36.423-g70) RACH report availability indication and Access and Mobility indication | Ericsson |
| R3-215228 | Reply LS on TCI state updates for L1/L2 centric inter-cell mobility | Ericsson |
| R3-215255 | Beam/Antenna Information for DL AoD | Ericsson LM |
| R3-215256 | [DRAFT] Reply LS on Beam/Antenna Information for DL AoD in NR Positioning | Ericsson LM |
| R3-215259 | Conclusions on Port Allocation for New Interfaces | Ericsson LM |
| R3-215260 | [DRAFT] Reply LS on Guidelines on Port Allocation for New 3GPP Interfaces | Ericsson LM |
| R3-215271 | (TP to TS 38.423 BL CR) RAN Multicast Group Paging | Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated |
| R3-215276 | [Draft] Reply LS on the MBS broadcast service continuity and MBS session | Lenovo, Motorola Mobility |
| R3-215294 | Discussion on multicast group paging | LG Electronics |
| R3-215295 | (TP for NR_MBS BL CR for TS 38.413) Discussion on multicast group paging | LG Electronics |
| R3-215296 | (TP for NR_MBS BL CR for TS 38.470) Discussion on multicast group paging | LG Electronics |
| R3-215300 | (TP for NR_MBS BL CR for TS 38.473) Discussion on multicast group paging | LG Electronics |
| R3-215324 | Handling of CAG restrictions at 4g to 5g handover | Nokia, Nokia Shanghai Bell |
| R3-215329 | Correction of CAG restriction at 4g to 5g handover | Nokia, Nokia Shanghai Bell |
| R3-215333 | Reply LS on Clarification of UE with CAG information in UE subscription | Nokia, Nokia Shanghai Bell |
| R3-215334 | Discussion on support the UE Radio Capability for Paging in RACS context | Nokia, Nokia Shanghai Bell, Vodafone |
| R3-215335 | (NGAP CR) support the UE Radio Capability for Paging in RACS context | Nokia, Nokia Shanghai Bell, Vodafone |
| R3-215336 | (S1AP CR) support the UE Radio Capability for Paging in RACS context | Nokia, Nokia Shanghai Bell, Vodafone |
| R3-215337 | [Draft] Reply LS on the UE Radio Capability for Paging in RACS context | Nokia |
| R3-215371 | Reply LS on PSCELL ID availability in SGW CDR | ETSI TC LI |
| R3-215377 | Discussion on PRS measurement outside the management gap | Huawei |
| R3-215378 | Discussion on beam/antenna information for DL-AOD in NR positioning | Huawei |
| R3-215379 | Discussion on misalignment in SRS configuration | Huawei |
| R3-215380 | Draft reply LS on alignment in SRS configuration | Huawei |
| R3-215381 | Discussion on local coordinates | Huawei, Ericsson |
| R3-215382 | [DRAFT] Reply LS on local coordinates | Huawei |
| R3-215383 | Supporting local coordinates for LTE RAT-dependent positioning | Huawei |
| R3-215384 | Clarification on local coordinates for E-CID | Huawei, Ericsson |
| R3-215395 | UE Radio Capability for Paging in RACS context | Huawei, Deutsche Telekom |
| R3-215396 | UE Radio Capability for Paging in RACS context - Local transcoding | Huawei, Deutsche Telekom |
| R3-215397 | UE Radio Capability for Paging in RACS context | Huawei, Deutsche Telekom |
| R3-215398 | UE Radio Capability for Paging in RACS context | Huawei, Deutsche Telekom |
| R3-215399 | [Draft] Reply LS on the UE Radio Capability for Paging in RACS context | Huawei |
| R3-215416 | Discussion on the scope of the UE Subgrouping for paging in RAN3 based on the RAN2 LS | Ericsson |
| R3-215417 | Discussion on the SA2 LS on the UE Radio Capability for Paging in RACS context | Ericsson |
| R3-215418 | Addition of UE Radio Capability for Paging for NR to S1-AP | Ericsson |
| R3-215429 | Overview of the received positioning liaisons | Ericsson |
| R3-215430 | Discussion on the RAN2 LS about SRS configuration misalignment between NRPPa and RRC and other issues | Ericsson |
| R3-215431 | Correction of Spatial Relation Information for SRS Configuration | Ericsson |
| R3-215432 | Correction of Spatial Relation Information for SRS Configuration | Ericsson |
| R3-215433 | draft reply LS to RAN2 on the misalignment in SRS configuration | Ericsson |
| R3-215434 | Discussion on the received LS on PRS measurement outside the measurement gap | Ericsson |
| R3-215435 | draft reply LS on PRS measurement outside the measurement gap | Ericsson |
| R3-215436 | TP to NRPPa BL CR: Addition of Positioning QoS | Ericsson |
| R3-215437 | TP to F1AP BL CR: Addition of Positioning QoS | Ericsson |
| R3-215483 | UE Security Capabilities signaling | Ericsson |
| R3-215484 | [DRAFT] Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | Ericsson |
| R3-215485 | UE Security Capabilities signaling in E-UTRAN | Ericsson |
| R3-215486 | UE Security Capabilities signaling in MR-DC | Ericsson |
| R3-215487 | UE Security Capabilities signaling in NG-RAN | Ericsson |
| R3-215488 | UE Security Capabilities signaling over S1 | Ericsson |
| R3-215489 | UE Security Capabilities signaling over X2 | Ericsson |
| R3-215490 | UE Security Capabilities signaling over NG | Ericsson |
| R3-215491 | UE Security Capabilities signaling over Xn | Ericsson |
| R3-215508 | Discussion on paging for multicast session activation notification | Samsung |
| R3-215509 | [Draft] Reply LS on paging for multicast session activation notification | Samsung |
| R3-215512 | (TP for BL CR for 38.413) Multicast Group Paging procedure in NG | Samsung |
| R3-215513 | (TP for BL CR for 38.423) Multicast Group Paging procedure in Xn | Samsung |
| R3-215514 | (TP for BL CR for 38.473) Multicast Group Paging procedure in F1 | Samsung |
| R3-215555 | Discussion on misalignment between RRC and NRPPa in SRS configuration | Samsung |
| R3-215556 | ReplyLS_Misalignment between RRC and NRPPa in SRS configuration | Samsung |
| R3-215557 | (CR for TS 38.455) spatial relation per SRS resource_for NRPPa | Samsung |
| R3-215558 | (CR for TS 38.473) spatial relation per SRS resource_for F1AP | Samsung |
| R3-215569 | Consideration on MBS broadcast service continuity and MBS session identification | Huawei |
| R3-215570 | [DRAFT] Reply LS on MBS broadcast service continuity and MBS session identification | Huawei |
| R3-215571 | Consideration on paging for multicast session activation notification | Huawei |
| R3-215572 | [DRAFT] Reply LS on paging for multicast session activation notification | Huawei |
| R3-215573 | Consideration on MBS latest progress and outstanding issues in SA WG | Huawei |
| R3-215574 | [Draft] Reply LS on latest progress and outstanding issues in SA WG2 | Huawei |
| R3-215575 | Paging subgrouping for UE power saving | Huawei |
| R3-215576 | Paging subgrouping for UE power saving | Huawei |
| R3-215577 | Paging subgrouping for UE power saving | Huawei |
| R3-215578 | Paging subgrouping for UE power saving | Huawei |
| R3-215579 | Supporting EPS User Plane Integrity Protection | Huawei, Orange |
| R3-215580 | Supporting EPS User Plane Integrity Protection | Huawei, Orange |
| R3-215581 | Supporting EPS User Plane Integrity Protection | Huawei, Orange |
| R3-215582 | Supporting EPS User Plane Integrity Protection | Huawei, Orange |
| R3-215583 | On UE security capability to address SA3 request | Huawei |
| R3-215584 | On UE security capability to address SA3 request [Sec_Capability] | Huawei |
| R3-215585 | On UE security capability to address SA3 request [Sec_Capability] | Huawei |
| R3-215586 | On UE security capability to address SA3 request [Sec_Capability] | Huawei |
| R3-215587 | [Draft] Reply LS on UE security capability | Huawei |
| R3-215603 | Consideration on the beamantenna information for DL AOD | CATT |
| R3-215604 | Reply LS on beam antenna information for DL AOD in NR positioning | CATT |
| R3-215624 | Discussion on UE paging subgroup | ZTE Corporation |
| R3-215625 | CR to TS38.413 for UE paging subgroup | ZTE Corporation |
| R3-215626 | CR to TS38.423 for UE paging subgroup | ZTE Corporation |
| R3-215627 | CR to TS38.473 for UE paging subgroup | ZTE Corporation |
| R3-215628 | [Draft] Reply LS on UE Power Saving | ZTE Corporation |
| R3-215629 | Discussion on EPS-5GS HO considering PNI-NPN restrictions | ZTE Corporation |
| R3-215634 | CR to TS38.413 for EPS-5GS HO considering PNI-NPN restrictions | ZTE Corporation |
| R3-215636 | [Draft] Reply LS on clarification of UE with CAG information in UE subscription | ZTE Corporation |
| R3-215638 | Discussion on the SRS misalignment | ZTE Corporation |
| R3-215640 | Correction to TS38.455 on misalignment in SRS configuration | ZTE Corporation |
| R3-215642 | UE Radio Capability for Paging in RACS context | Huawei, Deutsche Telekom |
| R3-215643 | Correction to TS38.473 on misalignment in SRS configuration | ZTE Corporation |
| R3-215649 | Reply LS (to R1-2108529) on Inter-donor migration | Huawei |
| R3-215650 | Reply LS (to R2-2109143) on Inter-donor migration | Huawei |
| R3-215651 | Discussion on the F1 interface for MOCN network sharing for multiple Cell Identity broadcast scenario | Huawei |
| R3-215652 | Reply LS (to S5-214652) on the F1 interface for MOCN network sharing for multiple Cell Identity broadcast scenariomigration | Huawei |
| R3-215653 | Guidelines on Port Allocation for New 3GPP Interfaces | Huawei |
| R3-215654 | Reply LS on Guidelines on Port Allocation for New 3GPP Inter | Huawei |
| R3-215717 | [Draft]Reply LS Reply on TCI State Update for L1L2-Centric Inter-Cell Mobility to RAN3 | ZTE |
| R3-215718 | (TP for SON BL CR for TS 36.413) SN RACH REPORT | ZTE |
| R3-215719 | (TP for SON BL CR for TS 36.423) SN RACH REPORT | ZTE |
| R3-215720 | (TP for SON BL CR for TS 38.413) SN RACH REPORT | ZTE |
| R3-215721 | Impact analysis of RACH report for SgNB and information needed for MRO in SCG Failure Report | ZTE |
| R3-215722 | Consideration on User Plane Integrity Protection for eUTRA connected to EPC | ZTE |
| R3-215723 | CR for TS 36.300 on UE Security Capabilities clarification | ZTE |
| R3-215724 | CR for TS 38.300 on UE Security Capabilities clarification | ZTE |
| R3-215725 | CR for TS 38.423 on UE Security Capabilities clarification | ZTE |
| R3-215726 | CR for TS 36.423 on UE Security Capabilities clarification | ZTE |
| R3-215727 | [Draft]Reply LS on Guidelines on Port Allocation for New 3GPP Interfaces | ZTE |
| R3-215765 | Discussion on the F1 interface for MOCN network sharing for multiple Cell Identity broadcast scenario | ZTE |
| R3-215766 | [Draft] Reply LS on the F1 interface for MOCN network sharing for multiple Cell Identity broadcast scenario | ZTE |
| R3-215790 | Reply LS on QoE Reference and maximum number of QoE configurations in RRC | SA5 |
| R3-215791 | Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions | SA5 |
| R3-215792 | Response to R3-215077 | HUAWEI Technologies Japan K.K. |
| R3-215793 | LS on Re-17 LTE and NR higher-layers parameter list | RAN1 |
| R3-215795 | LS Reply on UE Power Saving | SA2 |
| R3-215796 | LS Response on full registration request message to be rerouted via RAN | SA2 |
| R3-215798 | Reply LS on paging for multicast session activation notification | SA2 |
| R3-215800 | LS reply on UE assistance information for paging collision avoidance | SA2 |
| R3-215802 | Reply LS on MBS broadcast service continuity and MBS session identification | SA2 |
| R3-215804 | CB: # 1_PortAllocation - Summary of email discussion | Ericsson - moderator |
| R3-215805 | CB: # 2_L1L2CentricMobility - Summary of email discussion | ZTE - moderator |
| R3-215806 | CB: # 3_PositioningPRS - Summary of email discussion | Huawei - moderator |
| R3-215807 | CB: # 4_PositioningDLAOD - Summary of email discussion | CATT - moderator |
| R3-215808 | CB: # 5_PositioningSRS - Summary of email discussion | Ericsson - moderator |
| R3-215809 | CB: # 6_MBSProgressIssues_InSA2 - Summary of email discussion | Ericsson - moderator |
| R3-215810 | CB: # 7_MBSServContin_SessionID - Summary of email discussion | Huawei - moderator |
| R3-215811 | CB: # 8_MBSPaging - Summary of email discussion | ZTE - moderator |
| R3-215812 | CB: # 9_UEPowerSaving - Summary of email discussion | ZTE - moderator |
| R3-215813 | CB: # 10_CHOwithSCGConfig - Summary of email discussion | Nokia - moderator |
| R3-215814 | CB: # 11_SCGRACHReport - Summary of email discussion | Huawei - moderator |
| R3-215815 | CB: # 12_NPN4Gto5GHO_CAGInfor - Summary of email discussion | Nokia - moderator |
| R3-215816 | CB: # 13_RACS - Summary of email discussion | Ericsson - moderator |
| R3-215817 | CB: # 14_UPIPforEPC - Summary of email discussion | Qualcomm - moderator |
| R3-215818 | CB: # 15_NetworkSharing - Summary of email discussion | Huawei - moderator |
| R3-215872 | CB: # 76_PositioningLocalCodn - Summary of email discussion | Huawei - moderator |
| R3-215972 | (TP for BL CR for 38.413) Multicast group paging | ZTE |
| R3-215973 | (TP to TS 38.423 BL CR) RAN Multicast Group Paging | Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated |
| R3-215974 | (TP for BL CR for 38.473) Multicast Group Paging procedure in F1 | Samsung |
| R3-215975 | (TP for NR_MBS BL CR for TS 38.470) Discussion on multicast group paging | LG Electronics |
| R3-215976 | Reply LS on paging for multicast session activation notification | ZTE |
| R3-215977 | Reply LS on MBS broadcast service continuity and MBS session identification | Huawei |
| R3-215991 | (reserved) | ETSI-MCC |
| R3-215992 | [DRAFT] Reply LS on Guidelines on Port Allocation for New 3GPP Interfaces | Ericsson LM |
| R3-216009 | ReplyLS_Misalignment between RRC and NRPPa in SRS configuration | Samsung |
| R3-216010 | (CR for TS 38.455) spatial relation per SRS resource_for NRPPa | Samsung, Ericsson, ZTE |
| R3-216011 | (CR for TS 38.473) spatial relation per SRS resource_for F1AP | Samsung, Ericsson, ZTE |
| R3-216043 | LS Response on beam/antenna information for DL AOD in NR positioning | CATT |
| R3-216047 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated, Ericsson, Huawei |
| R3-216048 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated, Ericsson, Huawei |
| R3-216049 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated, Ericsson, Huawei |
| R3-216050 | Support for mapping complete security capabilities from NAS [UE_Sec_Caps] | Qualcomm Incorporated, Ericsson, Huawei |
| R3-216052 | [DRAFT] Reply LS on paging for multicast session activation notification | Ericsson |
| R3-216055 | Clarification of UE with CAG information in UE subscription | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-216056 | UE Security Capabilities signaling in E-UTRAN | Ericsson, Qualcomm Incorporated, Huawei |
| R3-216057 | UE Security Capabilities signaling in NG-RAN | Ericsson, Qualcomm Incorporated, Huawei |
| R3-216064 | Reply LS on clarification of UE with CAG information in UE subscription | Huawei |
| R3-216086 | (NGAP CR) support the UE Radio Capability for Paging in RACS context | Nokia, Nokia Shanghai Bell, Vodafone, Ericsson, Huawei, Deutsche Telekom, Qualcomm Incorporated |
| R3-216087 | (S1AP CR) support the UE Radio Capability for Paging in RACS context | Nokia, Nokia Shanghai Bell, Vodafone, Ericsson, Huawei, Deutsche Telekom, Qualcomm Incorporated |
| R3-216095 | On UE security capability to address SA3 request [Sec_Capability] | Huawei, Ericsson, Qualcomm Incorporated |
| R3-216127 | Clarification on local coordinates for E-CID [PosLocCoord] | Huawei, Ericsson |
| R3-216128 | Draft reply LS on location estimates in local co-ordinates | Huawei |
| R3-216134 | [DRAFT] Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | Qualcomm Incorporated |
| R3-216145 | (TP for SON BLCR for TS 38.423): TP on SCG RA report | Huawei |
| R3-216151 | (TP on SON for 36.423) TP on SCG RA report | CATT |
| R3-216166 | Reply LS (to S5-214652) on the F1 interface for MOCN network sharing for multiple Cell Identity broadcast scenariomigration | Huawei |
| R3-216168 | [Draft] Reply LS Reply on TCI State Update for L1L2-Centric Inter-Cell Mobility to RAN3 | ZTE |
| R3-216182 | CB: # 15_NetworkSharing - Summary of email discussion | Huawei - moderator |
| R3-216183 | CB: # 13_RACS - Summary of email discussion | Ericsson - moderator |
| R3-216200 | (TP on SON for 36.423) TP on SCG RA report | CATT |
| R3-216204 | CB: # 11_SCGRACHReport - Summary of email discussion | Huawei - moderator |
| R3-216212 | CB: # 8_MBSPaging - Summary of email discussion | ZTE - moderator |
| R3-216213 | Reply LS on paging for multicast session activation notification | ZTE |
| R3-216217 | CB: # 15_NetworkSharing - Summary of email discussion | Huawei - moderator |
| R3-216218 | Reply LS (to S5-214652) on the F1 interface for MOCN network sharing for multiple Cell Identity broadcast scenariomigration | Huawei |
| R3-216233 | Reply LS on Guidelines on Port Allocation for New 3GPP Interfaces | Ericsson LM |
| R3-216234 | Reply LS on TCI State Update for L1L2-Centric Inter-Cell Mobility to RAN3 | ZTE |
| R3-216235 | Reply LS on location estimates in local co-ordinates | Huawei |
| 8.2 | LSin received during the meeting | |
| R3-216109 | Reply LS on Area scope configuration and Frequency band info in MDT configuration | RAN2 |
| R3-216110 | Reply LS on MDT M6 calculation for split bearers in MR-DC | RAN2 |
| R3-216111 | Reply LS on downlink unmapped QoS flows | RAN2 |
| 8.3.1 | Inter-MN handover without SN change | |
| R3-214757 | Discussion on inter-MN handover without SN change | ZTE |
| R3-214758 | Clarification on inter-MN handover without SN change in Rel-15 | ZTE |
| R3-214759 | Clarification on inter-MN handover without SN change in Rel-16 | ZTE |
| R3-214760 | [DRAFT] Reply LS on inter-MN handover without SN change | ZTE |
| R3-214803 | Indication for full or delta configuration in case of a HO without SN change | Nokia, Nokia Shanghai Bell |
| R3-214804 | Clarification of the RRC config preparation in case of a HO without SN change | Nokia, Nokia Shanghai Bell |
| R3-214805 | Clarification of the RRC config preparation in case of a HO without SN change | Nokia, Nokia Shanghai Bell |
| R3-214806 | Response LS on inter-MN handover without SN change | Nokia, Nokia Shanghai Bell |
| R3-214933 | Inter MN handover without SN change and proposed draft response LS | NEC |
| R3-214988 | Consideration on inter-MN handover without SN change | Huawei |
| R3-214989 | Clarification on delta or full RRC configuration in inter-MN handover without SN change | Huawei |
| R3-214990 | Clarification on delta or full RRC configuration in inter-MN handover without SN change | Huawei |
| R3-214991 | [DRAFT] LS on inter-MN handover without SN change | Huawei |
| R3-215047 | Discussion on the issue raised in the LS R2-2106682 | CATT |
| R3-215048 | [Draft] Reply LS on inter-MN handover without SN change | CATT |
| R3-215288 | RRC configuration during inter-MN handover without SN change | Ericsson |
| R3-215289 | [DRAFT] Reply LS on inter-MN handover without SN change | Ericsson |
| R3-215290 | Introducing RRC configuration indicator during inter-MN handover without SN change | Ericsson |
| R3-215291 | Introducing RRC configuration indicator during inter-MN handover without SN change | Ericsson |
| R3-215292 | Introducing RRC configuration indicator during inter-MN handover without SN change | Ericsson |
| R3-215293 | Introducing RRC configuration indicator during inter-MN handover without SN change | Ericsson |
| R3-215510 | Discussion on the Inter-MN HO without SN change | Samsung |
| R3-215511 | [Draft] Reply LS on inter-MN handover without SN change | Samsung |
| R3-215819 | CB: # 16_InterMNHO_withoutSNChange - Summary of email discussion | Huawei - moderator |
| R3-216025 | [DRAFT] LS on inter-MN handover without SN change | Huawei |
| R3-216165 | Reply LS on inter-MN handover without SN change | Huawei |
| 8.3.2 | Bearer Pre-emption Rate Limit | |
| R3-215338 | Discussion on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Nokia, Nokia Shanghai Bell, BT, BDBOS, BMWi, Home Office, Firstnet, UIC, AT&T |
| R3-215339 | S1AP Cause value for exceeding the bearer pre-emption rate limitation | Nokia, Nokia Shanghai Bell, BT, BDBOS, BMWi, Home Office, Firstnet, UIC, AT&T |
| R3-215340 | NGAP Cause value for exceeding the bearer pre-emption rate limitation | Nokia, Nokia Shanghai Bell, BT, BDBOS, BMWi, Home Office, Firstnet, UIC, AT&T |
| R3-215341 | W1AP Cause value for exceeding the bearer pre-emption rate limitation | Nokia, Nokia Shanghai Bell, BT, BDBOS, BMWi, Home Office, Firstnet, UIC, AT&T |
| R3-215342 | F1AP Cause value for exceeding the bearer pre-emption rate limitation | Nokia, Nokia Shanghai Bell, BT, BDBOS, BMWi, Home Office, Firstnet, UIC, AT&T |
| R3-215343 | [Draft] Reply LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Nokia |
| R3-215400 | Bearer Pre-Emption for Mission-Critical Services in LTE | Ericsson LM |
| R3-215463 | [DRAFT] Reply LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Ericsson LM |
| R3-215549 | Discussion on Pre-emption limit issue in MC systems | Samsung |
| R3-215550 | (CR for TS 36.413) Support to address pre-emption limit issue in MC systems | Samsung |
| R3-215551 | (CR for TS 38.413) Support to address pre-emption limit issue in MC systems | Samsung |
| R3-215552 | ReplyLS_Pre-emption limit issue in MC systems | Samsung |
| R3-215655 | Further discussions on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Huawei |
| R3-215656 | Draft reply LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Huawei |
| R3-215820 | CB: # 17_BearerPreemptionRateLimit - Summary of email discussion | Nokia - moderator |
| R3-215918 | Bearer Pre-Emption for Mission-Critical Services in LTE | Ericsson LM |
| R3-215919 | [DRAFT] Reply LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Ericsson LM |
| R3-216088 | S1AP Cause value for exceeding the bearer pre-emption rate limitation | Nokia, Nokia Shanghai Bell, BT, BDBOS, BMWi, Home Office, Firstnet, UIC, AT&T |
| R3-216089 | [Draft] Reply LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Nokia |
| R3-216196 | Reply LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | Nokia |
| 8.3.3 | E-RABs Cannot Be Handed Over | |
| R3-214970 | Handling E-RABs which cannot be handed over to 3g | Nokia, Nokia Shanghai Bell |
| R3-214971 | Correction of Inter-RAT handover to 3g involving NR | Nokia, Nokia Shanghai Bell |
| R3-215151 | Indicating E-RABs that cannot be handed over to 5G | Ericsson, BT, Vodafone |
| R3-215152 | Indicating E-RABs that cannot be handed over to 5G | Ericsson, BT, Vodafone |
| R3-215153 | Indicating E-RABs that cannot be handed over to 5G | Ericsson, BT, Vodafone |
| R3-215360 | On E-RABs that cannot be handed over for inter-system interworking | Huawei |
| R3-215361 | On E-RABs that cannot be handed over for inter-system interworking | Huawei |
| R3-215728 | Handover from 3G via 4G to 5G | ZTE |
| R3-215729 | E-RABs Cannot Be Handed Over | ZTE |
| R3-215730 | E-RABs Cannot Be Handed Over for S1AP | ZTE |
| R3-215731 | E-RABs Cannot Be Handed Over for X2AP | ZTE |
| R3-215821 | CB: # 18_ERABsCannotHO - Summary of email discussion | ZTE - moderator |
| R3-216169 | Reply LS on E-RABs that cannot be handed over to 2G3G or 5G | ZTE |
| 8.3.4 | Report Amount for M4, M5, M6, M7 | |
| R3-214722 | Reply LS on Report Amount for M4, M5, M6, M7 measurements | SA5 |
| R3-214860 | (TP for MDT BLCR for TS 38.413): Discussion on Reply LS on Report Amount for M4, M5, M6, M7 measurements | Huawei |
| R3-214861 | (TP for MDT BLCR for TS 38.423): Introducing Report Amount for M4, M5, M6, M7 measurements | Huawei |
| R3-214862 | (TP for MDT BLCR for TS 38.473): Introducing Report Amount for M4, M5, M6, M7 measurements | Huawei |
| R3-214863 | (TP for MDT BLCR for TS 38.463): Introducing Report Amount for M4, M5, M6, M7 measurements | Huawei |
| R3-215401 | (draft) Reply LS to RAN2 and SA5 on Report Amount for M4, M5, M6, M7 measurements | Ericsson |
| R3-215402 | Discussion on the introduction of the Report Amount in MDT Measurements | Ericsson |
| R3-215403 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215404 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215405 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215406 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215407 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215408 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215409 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215410 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215411 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215412 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215732 | Report Amount for M4, M5, M6, M7 measurements | ZTE |
| R3-215733 | TP for 38.413 Report Amount for M4, M5, M6, M7 measurements | ZTE |
| R3-215734 | TP for 38.423 Report Amount for M4, M5, M6, M7 measurements | ZTE |
| R3-215735 | TP for 38.463 Report Amount for M4, M5, M6, M7 measurements | ZTE |
| R3-215736 | TP for 38.473 Report Amount for M4, M5, M6, M7 measurements | ZTE |
| R3-215822 | CB: # 19_MDTReportAmount - Summary of email discussion | Ericsson - moderator |
| R3-215926 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215927 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215928 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-215929 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-216026 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-216027 | Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-216073 | CR for the introduction of the Report Amount in MDT measurement configurations in TS38.423 | ZTE |
| R3-216146 | (TP for MDT BLCR for TS 38.473): Introducing Report Amount for M4, M5, M6, M7 measurements | Huawei |
| R3-216174 | CB: # 19_MDTReportAmount - Summary of email discussion | Ericsson - moderator |
| R3-216210 | (TP for MDT BLCR for TS 38.413) Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-216211 | (TP for MDT BLCR for TS 38.463) Introduction of the Report Amount in MDT measurement configurations | Ericsson |
| R3-216216 | (TP for MDT BLCR for TS 38.423): Introducing Report Amount for M4, M5, M6, M7 measurements | ZTE |
| 9.2.1 | Others | |
| R3-215564 | Clarification on the Reset procedure | Huawei, Orange |
| R3-215565 | Clarification on Reset Procedure | Huawei, Orange |
| R3-215566 | Clarification on Reset Procedure | Huawei, Orange |
| R3-215567 | Clarification on Reset Procedure | Huawei, Orange |
| R3-215568 | Clarification on Reset Procedure | Huawei, Orange |
| R3-215931 | CB: # 103_ResetCorrec - Summary of email discussion | Huawei - moderator |
| 9.3.1 | NR-NR DC Configuration Release | |
| R3-214850 | Discussion on NR-NR DC Configuration Release | ZTE |
| R3-214851 | Clarification for SgNB trigger SCG release in Rel-15 in TS 37.340 | ZTE |
| R3-214852 | Clarification for SgNB trigger SCG release in Rel-16 in TS 37.340 | ZTE |
| R3-214853 | Clarification for SgNB trigger SCG release in Rel-15 in TS 36.423 | ZTE |
| R3-214854 | Clarification for SgNB trigger SCG release in Rel-16 in TS 36.423 | ZTE |
| R3-214855 | [DRAFT] Reply LS on signalling SN initiated release of SCG | ZTE |
| R3-214934 | Proposed Response LS to RAN2 on Signalling SN initiated release of SCG resource and clarification CR | NEC |
| R3-214935 | Clarification for SgNB trigger SCG release | NEC |
| R3-214936 | Clarification for SgNB trigger SCG release | NEC |
| R3-214992 | Further discussion on SCG release | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-214993 | [DRAFT] LS on signalling SN initiated release of SCG | Huawei |
| R3-214994 | Clarification on SCG release indication | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-214995 | Clarification on SCG release indication | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-214996 | SN triggerred SCG release | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-214997 | SN triggerred SCG release | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-215158 | How to release SCG configuration between MN and SN over X2 | Ericsson |
| R3-215177 | How to release SCG configuration between MN and SN over X2 CR 36.423 | Ericsson |
| R3-215178 | How to release SCG configuration between MN and SN over X2 CR 36.423 | Ericsson |
| R3-215823 | CB: # 20_SCGConfigRelease - Summary of email discussion | ZTE - moderator |
| R3-215961 | Clarification for SgNB trigger SCG release in Rel-15 in TS 37.340 | ZTE, NEC, Erisson, Huawei |
| R3-215962 | Clarification for SgNB trigger SCG release in Rel-16 in TS 37.340 | ZTE, NEC, Erisson, Huawei |
| R3-215963 | Reply LS on signalling SN initiated release of SCG | Ericsson |
| R3-215964 | SN triggerred SCG release | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell, NEC, Erisson, ZTE |
| R3-215965 | SN triggerred SCG release | Huawei, Deutsche Telekom, Nokia, Nokia Shanghai Bell, NEC, Erisson, ZTE |
| R3-216236 | Reply LS on signalling SN initiated release of SCG | Ericsson |
| 9.3.2.1 | E1 Aspects | |
| R3-214770 | Support of 4g-5g direct data forwarding over E1 with non-shared gNB | Nokia, Nokia Shanghai Bell, China Telecom, CATT |
| R3-214771 | Support of 4g-5g direct data forwarding over E1 with non-shared gNB | Nokia, Nokia Shanghai Bell, China Telecom, CATT |
| R3-214772 | Allocation of TNL addresses for intra-system direct forwarding | Nokia, Nokia Shanghai Bell, Orange, China Telecom, CATT |
| R3-214773 | Allocation of TNL addresses for intra-system direct forwarding | Nokia, Nokia Shanghai Bell, Orange, China Telecom, CATT |
| R3-215362 | Direct data forwarding for 4G to 5G handover | Huawei, Samsung, China Telecom |
| R3-215363 | Direct data forwarding indication for intra-5GS handover | Huawei, Deutsche Telekom |
| R3-215364 | Direct data forwarding indication for intra-5GS handover | Huawei, Deutsche Telekom |
| R3-215480 | E1 aspects of inter-system direct data forwarding | Ericsson |
| R3-215536 | Direct data forwarding for inter-system HO from 4G to 5G | Samsung, LGU+, Huawei |
| R3-215615 | LS on indication of direct data forwarding availability | CATT,Nokia, Nokia Shanghai Bell,China Telecom |
| R3-215670 | Allocation of TNL addresses for intra-system data forwarding | China Telecom, CATT, Nokia, Nokia Shanghai Bell |
| R3-215824 | CB: # 21_DirectDataFwd_E1aspects - Summary of email discussion | Huawei - moderator |
| R3-216096 | Allocation of TNL addresses for intra-system data forwarding | China Telecom, CATT, Nokia, Nokia Shanghai Bell, Samsung, Huawei |
| R3-216097 | Direct data forwarding indication for intra-5GS handover | Huawei, Deutsche Telekom, Samsung, China Telecom |
| R3-216098 | LS on indication of direct data forwarding availability | CATT, Nokia, Nokia Shanghai Bell, China Telecom |
| R3-216176 | LS on indication of direct data forwarding availability | CATT, Nokia, Nokia Shanghai Bell, China Telecom |
| 9.3.2.2 | With Mobility Between DC and SA | |
| R3-214918 | SN direct data forwarding | Qualcomm Incorporated |
| R3-214919 | SN direct data forwarding | Qualcomm Incorporated |
| R3-214923 | Direct data forwarding between SA and NSA | Qualcomm Incorporated, CATT |
| R3-215365 | Direct data forwarding for mobility between DC and SA | Huawei, Samsung, China Telecom |
| R3-215532 | Discussion on direct data forwarding for mobility between DC and SA | Samsung, Huawei |
| R3-215533 | Direct data forwarding for mobility between DC and SA | Samsung, Huawei |
| R3-215534 | Direct data forwarding from MR-DC connected to 5GC to E-UTRAN | Samsung, Huawei, Verizon Wireless, LGU+, Nokia, Nokia Shanghai Bell |
| R3-215535 | Correction of Direct data forwarding from MR-DC connected to 5GC to E-UTRAN | Samsung, Huawei, Verizon Wireless, LGU+, Nokia, Nokia Shanghai Bell |
| R3-215616 | Discussion on data forwarding between DC and SA | CATT,Qualcomm |
| R3-215617 | CR on data forwarding between DC and SA | CATT,Qualcomm |
| R3-215781 | Direct data forwarding for mobility between DC and SA | Huawei, Samsung |
| R3-215784 | Direct data forwarding for mobility between DC and SA | Samsung, Huawei |
| R3-215825 | CB: # 22_DirectDataFwd_DC - Summary of email discussion | Samsung - moderator |
| R3-216075 | Direct data forwarding for mobility between DC and SA | Huawei, Samsung, ZTE, CATT |
| R3-216188 | Correction of Direct data forwarding from MR-DC connected to 5GC to E-UTRAN | Samsung, Huawei, Verizon Wireless, LGU+, Nokia, Nokia Shanghai Bell |
| 9.3.3 | Lossless Intra-System HO in CP-UP Separation Scenario | |
| R3-215074 | Discussion on Lossless intra-system HO in disaggregated architecture and QoS flow Mapping over E1 | Nokia, Nokia Shanghai Bell |
| R3-215076 | Lossless intra-system HO in disaggregated architecture – Sol 3b | Nokia, Nokia Shanghai Bell |
| R3-215481 | Lossless Intra-System HO in CP-UP Separation Scenario | Ericsson |
| R3-215529 | Lossless intra-system HO in dis-aggregated gNB scenario | Samsung, Huawei, Intel Corporation, China Telecom, LGU+, ZTE |
| R3-215530 | Correction of intra-system HO in CP-UP separation scenario | Samsung, Huawei, Intel Corporation, China Telecom, LGU+, ZTE |
| R3-215531 | Correction of intra-system HO in CP-UP separation scenario | Samsung, Huawei, Intel Corporation, China Telecom, LGU+, ZTE |
| R3-215826 | CB: # 23_Lossless_Intra-systemHO - Summary of email discussion | Samsung - moderator |
| R3-216158 | Correction CR for 38.463 on lossless intra-system HO with QoS flow remapping in CP-UP separated scenario | Intel Corporation, Nokia, Nokia Shanghai Bell, Samsung, Huawei |
| R3-216203 | Correction CR for 38.463 on lossless intra-system HO with QoS flow remapping in CP-UP separated scenario | Intel Corporation, Nokia, Nokia Shanghai Bell, Samsung, Huawei, ZTE |
| R3-216283 | Correction CR for 38.463 on lossless intra-system HO with QoS flow remapping in CP-UP separated scenario | Intel Corporation, Nokia, Nokia Shanghai Bell, Samsung, Huawei, ZTE |
| 9.3.4 | Dynamic ACL | |
| R3-214856 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom, Ericsson |
| R3-214857 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom, Ericsson |
| R3-214858 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom, Ericsson |
| R3-214859 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, Ericsson |
| R3-215229 | Dynamic ACL over E1 CR 38.463 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-215230 | Dynamic ACL over E1 CR 38.463 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-215231 | Dynamic ACL over S1 CR 36.413 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-215232 | Dynamic ACL over S1 CR 36.413 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-215233 | Dynamic ACL over X2 CR 36.423 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-215234 | Dynamic ACL over X2 CR 36.423 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-215235 | Dynamic ACL over Xn CR 38.423 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-215236 | Dynamic ACL over Xn CR 38.423 | Ericsson, Deutsche Telekom, China Telecom, Huawei |
| R3-215317 | On the granularity of the source IP address for dynamic ACL | Nokia, Nokia Shanghai Bell |
| R3-215318 | Support of dynamic ACL for direct data forwarding | Nokia, Nokia Shanghai Bell |
| R3-215619 | Discussion on dynamic ACL | ZTE Corporation |
| R3-215801 | Reply LS On ACL support for Indirect Data Forwarding | SA2 |
| R3-215827 | CB: # 24_DynamicACL - Summary of email discussion | Ericsson - moderator |
| R3-216139 | LS On Source IP address clarifications | Ericsson |
| R3-216140 | Reply to Reply LS On ACL support for Indirect Data Forwarding | Ericsson |
| 9.3.5 | Inter MN resume without SN change | |
| R3-215238 | Inter MN Resume without SN Change | Qualcomm Incorporated, Huawei, China Telecom, T-Mobile USA |
| R3-215239 | Inter MN Resume without SN Change (CR to 38.423) | Qualcomm Incorporated, Huawei, China Telecom, T-Mobile USA |
| R3-215828 | CB: # 25_InterMNResume_withoutSNChange - Summary of email discussion | Qualcomm - moderator |
| 9.3.6.1 | Other Corrections | |
| R3-214756 | Clarification on Early status transfer | ZTE, Intel Corporation, Lenovo |
| R3-214761 | Clarification on F1 Setup-Removal Procedure for RAN Sharing | RadiSys, Reliance JIO, ZTE, Lenovo, Motorola Mobility |
| R3-214762 | Correction on F1 Setup-Removal Procedure for RAN Sharing in Rel-15 | RadiSys, Reliance JIO, ZTE, Lenovo, Motorola Mobility |
| R3-214774 | Correction of NG Handover | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-214775 | Correction of NG Handover | Nokia, Nokia Shanghai Bell, Deutsche telekom |
| R3-214776 | Correction of wildcard SD | Nokia, Nokia Shanghai Bell, CATT, AT&T, TMO-US, China Telecom, Deutsche Telekom, Verizon Wireless, China Mobile |
| R3-214777 | Correction of wildcard SD | Nokia, Nokia Shanghai Bell, CATT, AT&T, TMO-US, China Telecom, Deutsche Telekom, Verizon Wireless, China Mobile |
| R3-214778 | Correction of Data Volume Report | Nokia, Nokia Shanghai Bell, Orange |
| R3-214779 | Correction of Data Volume Report | Nokia, Nokia Shanghai Bell, Orange |
| R3-214795 | Correction on F1 Setup and F1 Removal for RAN Sharing in Rel-16 | ZTE, Radisys, Reliance JIO, Lenovo, Motorola Mobility |
| R3-214932 | DAPS Inconsistencies | Nokia, Nokia Shanghai Bell |
| R3-214937 | Adding reference for coding of Common Network Instance | NEC |
| R3-214938 | Adding reference for coding of Common Network Instance | NEC |
| R3-214939 | Adding reference for coding of Common Network Instance | NEC |
| R3-214982 | Discussion on MDT stage3 misalignment for the report interval IE of M1 configuration | ZTE |
| R3-214983 | Value range misalignmet for Report Interval IE of MDT M1 configuration (NGAP) | ZTE, Lenovo, Motorola Mobility, China Unicom, China Telecom, CATT |
| R3-214984 | Value range misalignment for Report Interval IE of MDT M1 configuration (XnAP) | ZTE, Lenovo, Motorola Mobility, China Unicom, China Telecom, CATT |
| R3-214998 | Correction on the usage of selected PLMN | Huawei, Deutsche Telekom, Orange |
| R3-214999 | Correction on the usage of selected PLMN | Huawei, Deutsche Telekom, Orange |
| R3-215009 | Correction on presence of extended Slice Support List | NTT DOCOMO INC. |
| R3-215011 | Discussion on removing the restriction of cause value of “procedure cancelled” | CATT |
| R3-215012 | Remove the restriction on cause value “procedure cancelled” for 38.423 (R15) | CATT |
| R3-215079 | Incorrect Node Name IE in ASN.1 | Nokia, Nokia Shanghai Bell, Verizon Wireless |
| R3-215084 | Discussion on including CN Support information in the CU-UP Configuration Update message (E1AP) | Samsung, SK Telecom, KT, LGU+, Verizon |
| R3-215087 | Addition of the CN Support IE in gNB-CU-UP configuration update message_Rel-15 | Samsung, SK Telecom, KT, LGU+, Verizon |
| R3-215088 | Addition of the CN Support IE in gNB-CU-UP configuration update message_Rel-16 | Samsung, SK Telecom, KT, LGU+, Verizon |
| R3-215160 | Retrieve UE context for NPN only cell | Huawei, Deutsche Telekom, Orange |
| R3-215161 | Correcion of QoS monitoring request and disabled | Huawei, ZTE, CMCC |
| R3-215162 | Correcion of QoS monitoring request and disabled | Huawei, ZTE, CMCC |
| R3-215163 | Inclusion of RFSP for NG-RAN | Huawei, China Telecom |
| R3-215164 | Correction for UL PDU Session Information | Huawei, China Telecom |
| R3-215165 | Correction for UL PDU Session Information | Huawei, China Telecom |
| R3-215166 | Correction of Paging DRX | Huawei, Orange, Deutsche Telekom |
| R3-215167 | Correction of Paging DRX | Huawei, Orange, Deutsche Telekom |
| R3-215168 | Correction of Paging DRX | Huawei, Orange, Deutsche Telekom |
| R3-215169 | Correction of Paging DRX | Huawei, Orange, Deutsche Telekom |
| R3-215170 | Correction of Paging DRX | Huawei, Orange, Deutsche Telekom |
| R3-215171 | Correction of Paging DRX | Huawei, Orange, Deutsche Telekom |
| R3-215172 | Extension of Index to RAT/Frequency Selection Priority | Huawei, Orange, Deutsche Telekom |
| R3-215182 | Discussion on the RRC container in HO REQ ACK message in CHO replace procedure | Samsung |
| R3-215184 | Addition of the new IE in HO REQ ACK message for CHO replace | Samsung |
| R3-215196 | Location Reporting (PS Reporting on XnAP) | Ericsson, Vodafone |
| R3-215197 | Location Reporting (PS Reporting on XnAP) | Ericsson, Vodafone |
| R3-215198 | Location Reporting (PS Reporting on X2AP) | Ericsson, Vodafone |
| R3-215199 | Location Reporting (PS Reporting on X2AP) | Ericsson, Vodafone |
| R3-215214 | Correction on Cell to be Broadcast List presence | Ericsson |
| R3-215215 | Correction on Cell to be Broadcast List presence | Ericsson |
| R3-215265 | Correction of PDU session resource modify | Huawei, China Unicom, Orange |
| R3-215266 | Correction of PDU session resource modify | Huawei, China Unicom, Orange |
| R3-215322 | Dual Connectivity Support at Inter-MN handover | Nokia, Nokia Shanghai Bell, Orange |
| R3-215323 | Dual Connectivity Support at Inter-MN handover | Nokia, Nokia Shanghai Bell, Orange |
| R3-215366 | Redundant network instance for split PDU session | Huawei, CATT, CMCC |
| R3-215367 | Redundant network instance for split PDU session | Huawei, CATT, CMCC |
| R3-215385 | LCS to GCS Translation alignment | Huawei, Ericsson |
| R3-215386 | LCS to GCS Translation alignment | Huawei, Ericsson |
| R3-215387 | ASN.1 correction and alignement in tabular | Huawei, Ericsson |
| R3-215388 | Correction on PRS-only TP | Huawei, CMCC, Ericsson |
| R3-215389 | Correction on PRS-only TP | Huawei, CMCC, Ericsson, Qualcomm Incorporated |
| R3-215465 | Correction on UE Context Modification | Ericsson |
| R3-215466 | Correction on UE Context Modification | Ericsson |
| R3-215467 | Correction on UE Context Modification | Ericsson |
| R3-215468 | Voice EPS Fallback and VoNR | Ericsson |
| R3-215469 | Voice EPS Fallback and VoNR | Ericsson |
| R3-215470 | Voice EPS Fallback and VoNR | Ericsson |
| R3-215471 | Discussion on NR Handover and Data forwarding | Ericsson |
| R3-215472 | Avoiding unencrypted radio interface data transfer | VODAFONE |
| R3-215498 | Discussion of QoS Mapping Information in E1 for IAB | Samsung, ZTE, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-215499 | Correction of Qos Mapping Information IE in E1AP message for IAB (CR to TS38.463, R16) | Samsung, ZTE, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-215500 | Discussion for CHO early data forwarding | Samsung, Intel, CATT |
| R3-215501 | E1 impact to support to stop CHO early data forwarding | Samsung, Intel, CATT |
| R3-215505 | Discussion on the correction to S-NODE MODIFICATION REQUIRED message | Samsung, Verizon Wireless |
| R3-215506 | Correction to S-NODE MODIFICATION REQUIRED message | Samsung, Verizon Wireless |
| R3-215507 | Correction to S-NODE MODIFICATION REQUIRED message | Samsung, Verizon Wireless |
| R3-215559 | Discussion on F1-U Delay Measurement for QoS Monitoring | Samsung, Verizon Wireless |
| R3-215560 | Correction of F1-U delay measurement for QoS monitoring 1 | Samsung, Verizon Wireless |
| R3-215588 | Provision of Mobility Restriction List in PATH SWITCH REQUEST ACKNOWLEDGE_v15 | CATT, China Telecom |
| R3-215589 | Provision of Mobility Restriction List in PATH SWITCH REQUEST ACKNOWLEDGE_v16 | CATT, China Telecom |
| R3-215618 | Correction on PDU Session Modify procedure | CATT,Huawei,China Telecom |
| R3-215645 | Correction to TS38.455 on SRS configuration | ZTE Corporation |
| R3-215687 | Correction of NAS PDU in PDU Session Modify | CMCC |
| R3-215715 | Cause value for no IP connectivity between T-RAN and S-UPF_R15 | ZTE, China Unicom, China Telecom |
| R3-215716 | Cause value for no IP connectivity between T-RAN and S-UPF | ZTE, China Unicom, China Telecom |
| R3-215737 | Discussion on Criticality Diagnostics over W1 | ZTE, China Telecom, China Unicom |
| R3-215738 | Correction on Criticality Diagnostics over W1 | ZTE, China Telecom, China Unicom |
| R3-215752 | PDU session NAS PDU Delivery | ZTE |
| R3-215829 | CB: # 26_NGHandover - Summary of email discussion | Nokia - moderator |
| R3-215830 | CB: # 27_ReportIntervalMDT - Summary of email discussion | ZTE - moderator |
| R3-215831 | CB: # 28_F1-UDelay - Summary of email discussion | Samsung - moderator |
| R3-215832 | CB: # 29_PDUSessModCorrections - Summary of email discussion | CMCC - moderator |
| R3-215833 | CB: # 30_PositionCorrections - Summary of email discussion | Huawei - moderator |
| R3-215914 | Correction on PRS-only TP | Huawei, CMCC, Ericsson |
| R3-215915 | Correction on PRS-only TP | Huawei, CMCC, Ericsson |
| R3-215930 | Correction on UE Context Modification | Ericsson |
| R3-215932 | CB: # 104_F1Setup_Removal - Summary of email discussion | RadiSys - moderator |
| R3-215933 | DAPS Inconsistencies | Nokia, Nokia Shanghai Bell |
| R3-215934 | Correction of Data Volume Report | Nokia, Nokia Shanghai Bell, Orange |
| R3-215935 | Correction of Data Volume Report | Nokia, Nokia Shanghai Bell, Orange |
| R3-215936 | CB: # 105_ComNetwork_Instance - Summary of email discussio | NEC - moderator |
| R3-215937 | Incorrect Node Name IE in ASN.1 | Nokia, Nokia Shanghai Bell, Verizon Wireless |
| R3-215938 | Redundant network instance for split PDU session | Huawei, CATT, CMCC, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-215939 | Redundant network instance for split PDU session | Huawei, CATT, CMCC, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-215940 | CB: # 108_NewXnAP_Cause - Summary of email discussion | ZTE - moderator |
| R3-215942 | CB: # 109_CHO_EarlyDataForward - Summary of email discussion | Samsung - moderator |
| R3-215943 | CB: # 110_NPNonlyCell - Summary of email discussion | Huawei - moderator |
| R3-215944 | CB: # 111_ULPDUSession - Summary of email discussion | Huawei - moderator |
| R3-215945 | Correction to S-NODE MODIFICATION REQUIRED message | Samsung, Verizon Wireless |
| R3-215946 | CB: # 112_CriticallityDiag - Summary of email discussion | ZTE - moderator |
| R3-216004 | Correction for UL PDU Session Information | Huawei, China Telecom |
| R3-216005 | Correction for UL PDU Session Information | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-216031 | Adding reference for coding of Common Network Instance | NEC, Ericsson |
| R3-216032 | Adding reference for coding of Common Network Instance | NEC, Ericsson |
| R3-216033 | Adding reference for coding of Common Network Instance | NEC, Ericsson |
| R3-216083 | Correction of NG Handover | Nokia, Nokia Shanghai Bell, Deutsche telekom |
| R3-216094 | CB: # 106_NodeName - Summary of email discussion | Nokia |
| R3-216099 | Correction on Criticality Diagnostics over W1 | ZTE, China Telecom, China Unicom |
| R3-216124 | ASN.1 Correction | Huawei, Ericsson |
| R3-216125 | Correction on PRS-only TP | Huawei, CMCC, Ericsson, Qualcomm Incorporated |
| R3-216126 | Correction on PRS-only TP | Huawei, CMCC, Ericsson, Qualcomm Incorporated |
| R3-216152 | Correction on F1 Setup-Removal Procedure for RAN Sharing in Rel-15 | Radisys, Reliance JIO, ZTE, Lenovo, Motorola Mobility, Ericsson, Nokia, Nokia Shanghai Bell, InterDigital |
| R3-216153 | Correction on F1 Setup and F1 Removal for RAN Sharing in Rel-16 | ZTE, Radisys, Reliance JIO, Lenovo, Motorola Mobility, Ericsson, Nokia, Nokia Shanghai Bell, InterDigital |
| R3-216154 | Correction on Xn Removal for RAN Sharing in Rel-15 | Radisys, Reliance JIO, ZTE, Lenovo, Motorola Mobility, Ericsson, Nokia, Nokia Shanghai Bell, InterDigital |
| R3-216155 | Correction on Xn Removal for RAN Sharing in Rel-16 | ZTE, Radisys, Reliance JIO, Lenovo, Motorola Mobility, Ericsson, Nokia, Nokia Shanghai Bell, InterDigital |
| R3-216156 | Correction on EN-DC X2 Removal for RAN Sharing in Rel-15 | Ericsson, Radisys, Reliance JIO, ZTE, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, InterDigital |
| R3-216157 | Correction on EN-DC X2 Removal for RAN Sharing in Rel-16 | Ericsson, ZTE, Radisys, Reliance JIO, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, InterDigital |
| R3-216161 | Incorrect Node Name IE in ASN.1 | Nokia, Nokia Shanghai Bell, Verizon Wireless |
| R3-216162 | DAPS Inconsistencies | Nokia, Nokia Shanghai Bell |
| R3-216163 | Value range misalignment for Report Interval IE of MDT M1 configuration (NGAP) [TEI16] | ZTE, Lenovo, Motorola Mobility, China Unicom, China Telecom, CATT, CMCC |
| R3-216164 | Value range misalignment for Report Interval IE of MDT M1 configuration (XnAP) [TEI16] | ZTE, Lenovo, Motorola Mobility, China Unicom, China Telecom, CATT, CMCC |
| R3-216170 | Error indication on no IP connectivity between T-RAN and S-UP | ZTE |
| R3-216181 | E1 impact to support to stop CHO early data forwarding | Samsung, Intel Corporation, CATT |
| R3-216209 | Update Cause value for no IP connectivity between T-RAN and S-UPF | ZTE |
| R3-216239 | Incorrect Node Name IE in ASN.1 | Nokia, Nokia Shanghai Bell, Verizon Wireless |
| R3-216284 | DAPS Inconsistencies | Nokia, Nokia Shanghai Bell |
| R3-216285 | Incorrect Node Name IE in ASN.1 | Nokia, Nokia Shanghai Bell, Verizon Wireless |
| 9.3.6.2 | Pure Stage-2 Corrections | |
| R3-214893 | Clarification of DC scenarios allowed in PNI-NPN | Qualcomm Incorporated |
| R3-214894 | Handling of mobility and dual connectivity in mixed PNI-NPN/PLMN cell scenarios | Qualcomm Incorporated |
| R3-215022 | Correction on SN-initiated SN Release | Google Inc. |
| R3-215023 | Correction on SN-initiated SN Release | Google Inc. |
| R3-215502 | DL Xn-U address transfer in E1 interface for SN terminated MCG/split bearer | Samsung, ZTE, Huawei |
| R3-215503 | Correction the text of stage 2 for DL Xn-U address information transfer (CR to TS 38.401, R15) | Samsung, ZTE, Huawei |
| R3-215504 | Correction the text of stage 2 for DL Xn-U address information transfer (CR to TS 38.401, R16) | Samsung, ZTE, Huawei |
| R3-215744 | CR for 38.460 on E1AP handling for unmapped DL QoS flows | Intel Corporation, CATT, Huawei, Nokia, Nokia Shanghai Bell |
| R3-215834 | CB: # 31_Stage2Corrections - Summary of email discussion | Nokia - moderator |
| R3-215843 | Clarification on Secondary RAT Data Usage Report for ENDC and MRDC | RadiSys, Reliance JIO |
| R3-215844 | Correction on Secondary RAT Data Usage Report for R15 | RadiSys |
| R3-216160 | Correction the text of stage 2 for DL Xn-U address information transfer (CR to TS 38.401, R16) | Samsung, ZTE, Huawei |
| R3-216177 | Correction on SN-initiated SN Release | Google Inc. |
| 10.1 | General | |
| R3-214606 | BLCR to 36.423:Support of MDT enhancement | CATT |
| R3-214607 | BLCR to 38.413_Addition of SON features enhancement | Ericsson |
| R3-214608 | MDT in MR-DC | Huawei |
| R3-214609 | BLCR to 36.413_Addition of SON features enhancement | Qualcomm |
| R3-214610 | BLCR to 36.300_Addition of SON features enhancement | Lenovo, Motorola Mobility |
| R3-214612 | BLCR to 37.320: Support of MDT enhancement | Nokia, Nokia Shanghai Bell |
| R3-214618 | MRO for PScell Change Failure | Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE |
| R3-214619 | BLCR to 38.401: Support of MDT enhancement | CMCC |
| R3-214620 | BLCR to 36.423_Addition of SON features enhancement | CATT |
| R3-214621 | BLCR to 38.463: Support of MDT enhancement | Nokia, Nokia Shanghai Bell |
| R3-214622 | BLCR to 38.473: Support of MDT enhancement | Samsung |
| R3-214628 | BLCR to 38.423_Addition of SON features enhancement | Samsung |
| R3-214629 | BLCR to 38.473_Addition of SON features enhancement | Huawei |
| R3-214654 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-214655 | BLCR to 38.401_Addition of SON features enhancement | ZTE |
| R3-215693 | Updated work plan for enhancement of data collection for SON_MDT in NR and EN-DC WI | CMCC, Ericsson |
| R3-215850 | CB: # SONMDT1_Workplan_BLCRs - Summary of email discussion | CMCC - moderator |
| R3-215941 | BLCR to 38.413_Addition of SON features enhancement | Ericsson |
| R3-216253 | BLCR to 36.423_Addition of SON features enhancement | CATT |
| R3-216254 | BLCR to 38.413_Addition of SON features enhancement | Ericsson |
| R3-216255 | BLCR to 38.423_Addition of SON features enhancement | Samsung |
| R3-216256 | BLCR to 38.473_Addition of SON features enhancement | Huawei |
| R3-216257 | BLCR to 37.320: Support of MDT enhancement | Nokia, Nokia Shanghai Bell |
| R3-216258 | MDT in MR-DC | Huawei |
| R3-216259 | BLCR to 38.463: Support of MDT enhancement | Nokia, Nokia Shanghai Bell |
| R3-216280 | BLCR to 38.473: Support of MDT enhancement | Samsung |
| R3-216281 | BLCR to 36.413_Addition of SON features enhancement | Qualcomm |
| R3-216282 | BLCR to 38.413: Support of MDT enhancement | Ericsson |
| 10.2.1.3 | Successful Handover Report | |
| R3-215065 | Discussion on correlating SHR with RLF Report for DAPS MRO | CATT |
| 10.2.1.4 | UE History Information in EN-DC | |
| R3-214811 | [SON BL CRs, TP to TS 38.423, TP to TS 36.423] HO delay and non-up-to-date SCG UHI information | Nokia, Nokia Shanghai Bell |
| R3-214840 | Consideration on UE history information | China Telecommunication |
| R3-214915 | UE History Information in MR-DC | Qualcomm Incorporated |
| R3-214956 | (TP for SON BLCR for 38.423,38.413, 36.423, 36.413 , 37.340, 38.300) UE History Information in MR-DC | Huawei |
| R3-215068 | Enhancement of UE history information in MR-DC scenario | CATT,CMCC |
| R3-215069 | (TP on UE history information for 36.413) Addition of UE history information for SN | CATT,CMCC |
| R3-215070 | (TP on UE history information for 36.423) Addition of UE history information for SN | CATT,CMCC |
| R3-215444 | (TP for SON BL CR for TS 38.423, TS 38.413, TS 36.413): UE History Information for Secondary Node | Ericsson |
| R3-215456 | UE History Information in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-215457 | (TP for SON BL CR for TS 37.340) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-215458 | (TP for SON BL CR for TS 38.423) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-215459 | (TP for SON BL CR for TS 36.423) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-215460 | (TP for SON BL CR for TS 38.413) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-215461 | (TP for SON BL CR for TS 36.413) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-215519 | UE History Information in MR-DC | Samsung |
| R3-215520 | TP for SON BLCR for 38.423: UE History Information in MR-DC | Samsung |
| R3-215521 | TP for SON BLCR for 36.423: UE History Information in EN-DC | Samsung |
| R3-215695 | (TP to TS 38.413)UE history information in MR-DC | CMCC, CATT |
| R3-215696 | (TP to TS 38.423)UE history information in MR-DC | CMCC, CATT |
| R3-215851 | CB: # SONMDT2_UEHistoryInfor - Summary of email discussion | ZTE - moderator |
| R3-216006 | CB: # SONMDT2_UEHistoryInfor - Summary of email discussion | ZTE - moderator |
| R3-216173 | (TP for SON BL CR for TS 36.423): UE History Information for Secondary Node | Ericsson, ZTE, CATT, Samsung |
| R3-216175 | (TP for SON BL CR for TS 38.423) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-216220 | (NR_ENDC_SON_MDT_enh, TP SON BL CR to TS 38.413) Addition of SCG UHI information | Nokia, Nokia Shanghai Bell, ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-216221 | (NR_ENDC_SON_MDT_enh, TP SON BL CR to TS 36.413) Addition of SCG UHI information | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-216223 | (TP for SON BL CR for TS 38.423) Introduce UHI in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom, Ericsson, Samsung, CATT, CMCC |
| 10.2.1.5 | Load Balancing Enhancements | |
| R3-214812 | [SON, TP to BL CR to TS 38.473] Further discussion on the CU-DU impacts of the per-beam mobility setting change | Nokia, Nokia Shanghai Bell |
| R3-214813 | [TP to SON BL CR to 38.423, NR_ENDC_SON_MDT_enh] Semantics for the PRB per slice description | Nokia, Nokia Shanghai Bell |
| R3-214946 | (TP for SON BLCR for 38.423) Load Balancing Enhancements: SUL reporting in Radio Resource Status | NEC |
| R3-214947 | (TP for SON BLCR for 38.473) Load Balancing Enhancements: SUL reporting in Radio Resource Status | NEC |
| R3-214957 | (TP for SON BLCR for 38.423, 38.473) Load Balancing Enhancements | Huawei |
| R3-215040 | Discussion on PSCell MLB | CATT |
| R3-215052 | Discussion on PSCell MLB | CATT |
| R3-215176 | Discussion on per-SSB and per-slice Mobility Settings Change | NEC |
| R3-215445 | (TP for SON BL CR for TS 38.423) MLB enhancements | Ericsson |
| R3-215446 | (TP for SON BL CR for TS 36.423) MLB enhancements | Ericsson |
| R3-215769 | Further Discussion on Load Balancing Enhancements in NR | ZTE,China Telecom, China Unicom |
| R3-215770 | TP for BL CR 38.423 on Load Balancing Enhancements | ZTE,China Telecom, China Unicom |
| R3-215771 | TP for BL CR 38.473 on Load Balancing Enhancements | ZTE,China Telecom, China Unicom |
| R3-215852 | CB: # SONMDT3_LoadBalance - Summary of email discussion | Nokia - moderator |
| R3-216001 | [TP to SON BL CR to 38.423, NR_ENDC_SON_MDT_enh] Semantics for the PRB per slice description | Nokia, Nokia Shanghai Bell, Huawei |
| R3-216007 | CB: # SONMDT3_LoadBalance - Summary of email discussion | Nokia - moderator |
| R3-216066 | (TP to SON BL CR to 38.473, NR_ENDC_SON_MDT_enh) Semantics for the PRB per slice description | Huawei, Nokia, Nokia Shanghai Bell |
| 10.2.1.6 | MRO for SN Change Failure | |
| R3-214814 | [TP to SON BL CR to 38.423, TP to SON BL CR to 36.423, NR_ENDC_SON_MDT_enh] MRO for PSCell change failure | Nokia, Nokia Shanghai Bell |
| R3-214841 | Consideration on MRO for SN Change Failure | China Telecommunication |
| R3-214916 | MRO for SN Change Failure | Qualcomm Incorporated |
| R3-214958 | (TP for SON BLCR for 38.423, 38.300) MRO for SN Change Failure | Huawei |
| R3-214985 | Further consideration on MRO SN change failure | ZTE |
| R3-214986 | (TP for SON BL CR for TS 38.423) MRO SN change failure | ZTE |
| R3-214987 | [draft] LS on MN awareness of Source PSCell CGI and Source PSCell CGI | ZTE |
| R3-215066 | (TP for 38.423) consideration on support of SN change failure in case of MR-DC | CATT |
| R3-215067 | Reply LS on information needed for MRO in SCG Failure Report | CATT |
| R3-215442 | MRO for SN change failure | Ericsson |
| R3-215443 | [DRAFT] Reply LS on RACH report for SgNB and information needed for MRO in SCG Failure Report | Ericsson |
| R3-215518 | TP for SON BLCR for TS38.423: Support of SON for SN change failure | Samsung |
| R3-215853 | CB: # SONMDT4_SNChangeFailure - Summary of email discussion | Samsung - moderator |
| R3-216008 | CB: # SONMDT4_SNChangeFailure - Summary of email discussion | Samsung - moderator |
| R3-216159 | Reply LS on scenarios need to be supported for MRO in SCG Failure Report | Samsung |
| 10.2.1.7 | RACH Optimization Enhancements | |
| R3-214864 | (TP for SON BL CR for TS 38.473): Left overs on RACH Optimization Enhancements | Huawei |
| R3-215053 | Discussion on Rel-16 leftover issues for PRACH coordination | CATT |
| R3-215054 | (TP on SON for 36.423) TP on PRACH coordination for X2AP | CATT |
| R3-215447 | (TP for SON BL CR for TS 38.473): RACH conflict resolution procedure | Ericsson |
| R3-215475 | Further discussion on down-selection of options for RACH optimization | Nokia, Nokia Shanghai Bell |
| R3-215476 | (TP for SON BL CR for TS 38.473) Enhancement of RACH Conflict Resolution | Nokia, Nokia Shanghai Bell |
| R3-215854 | CB: # SONMDT5_RACHOpt - Summary of email discussion | CATT - moderator |
| R3-216013 | CB: # SONMDT5_RACHOpt - Summary of email discussion | CATT - moderator |
| 10.2.2 | Coverage and Capacity Optimization | |
| R3-214917 | Coverage and Capacity Optimization | Qualcomm Incorporated |
| R3-214948 | CCO over F1: functional split and signaling between gNB-CU and gNB-DU | NEC |
| R3-214949 | (TP for SON BLCR 38.300) Coverage and Capacity Optimization | NEC |
| R3-214950 | (TP for SON BLCR for 38.473) Coverage and Capacity Optimization | NEC |
| R3-214959 | (TP for SON BLCR for 38.473, 38.401,38.300, 38.470) Coverage and Capacity Optimization | Huawei |
| R3-215314 | (TP for SON BL CR for TS 38.300) On CCO functional description | Nokia, Nokia Shanghai Bell |
| R3-215315 | (TP for SON BL CR for TS 38.401) On CCO functional description for split architecture | Nokia, Nokia Shanghai Bell |
| R3-215448 | (TP for SON BL CR for TS 38.300, TS 38.401) NR CCO solution and use cases | Ericsson |
| R3-215449 | (TP for SON BL CR for TS 38.423, TS 38.473) SSB coverage state and Measurements for CCO issue detection | Ericsson |
| R3-215517 | TP for SON BLCR for TS38.300: Support of SON for CCO | Samsung |
| R3-215772 | Further Discussion on Coverage and Capacity Optimization in NR | ZTE,China Telecom, China Unicom, Lenovo, Motorola Mobility |
| R3-215773 | TP for BL CR 38.300 on Coverage and Capacity Optimization | ZTE,China Telecom, China Unicom |
| R3-215774 | TP for BL CR 38.423 on Coverage and Capacity Optimization | ZTE,China Telecom, China Unicom, Lenovo, Motorola Mobility |
| R3-215775 | TP for BL CR 38.473 on Coverage and Capacity Optimization | ZTE,China Telecom, China Unicom, Lenovo, Motorola Mobility |
| R3-215855 | CB: # SONMDT6_CCO - Summary of email discussion | Ericsson - moderator |
| R3-216003 | LS on CCO parameters range | Ericsson |
| R3-216016 | CB: # SONMDT6_CCO - Summary of email discussion | Ericsson - moderator |
| R3-216189 | LS on CCO related assistance information from OAM to NG-RAN | Ericsson |
| 10.2.4 | Inter-System Load Balancing | |
| R3-214960 | (TP for SON BLCR for 38.413) Inter-System Load Balancing | Huawei |
| R3-215450 | (TP for SON for TS 38.413, TS 38.300, TS 36.300) Inter-System Load Balancing | Ericsson |
| R3-215683 | Further discussions on load metrics of inter-system load balancing | CMCC |
| R3-215684 | TP to SON BLCR 36.300 for inter-system load balancing | CMCC |
| R3-215685 | TP to SON BLCR 38.300 for inter-system load balancing | CMCC |
| R3-215686 | TP to SON BLCR 38.413 for inter-system load balancing | CMCC |
| R3-215776 | Further Discussion on Inter-system Load Balancing in NR | ZTE,China Telecom, Lenovo, Motorola Mobility |
| R3-215777 | TP for BL CR 36.300 on Inter-system Load Balancing | ZTE,China Telecom |
| R3-215778 | TP for BL CR 38.300 on Inter-system Load Balancing | ZTE,China Telecom, China Unicom |
| R3-215779 | TP for BL CR 38.413 on Inter-system Load Balancing | ZTE,China Telecom, China Unicom, Lenovo, Motorola Mobility |
| R3-215856 | CB: # SONMDT7_InterSystemLB - Summary of email discussion | Huawei - moderator |
| R3-216017 | CB: # SONMDT7_InterSystemLB - Summary of email discussion | Huawei - moderator |
| R3-216045 | (TP for SON BLCR for 38.413) Inter-System Load Balancing | Huawei |
| 10.2.6 | Mobility Enhancement Optimization | |
| R3-214961 | Mobility Enhancement Optimization | Huawei |
| R3-215063 | Discussion on MRO for mobility Enhancement | CATT |
| R3-215064 | (TP on MRO for 38.423) Failure Indication message enhancement for CHO | CATT |
| R3-215297 | SON Enhancements for CHO | Lenovo, Motorola Mobility, ZTE |
| R3-215298 | SON Enhancements for DAPS Handover | Lenovo, Motorola Mobility, ZTE |
| R3-215451 | (TP for SON BL CR for TS 38.300) MRO for CHO and DAPS | Ericsson |
| R3-215537 | Discussion on SON enhancements for CHO | Samsung |
| R3-215538 | TP for SON BLCR for TS38.300: SON enhancements for CHO | Samsung |
| R3-215539 | TP for SON BLCR for TS38.423: Support of CHO for MRO | Samsung |
| R3-215753 | Further consideratino on Mobility enhancement | ZTE |
| R3-215857 | CB: # SONMDT8_MobilityEnc - Summary of email discussion | Lenovo - moderator |
| R3-216018 | CB: # SONMDT8_MobilityEnc - Summary of email discussion | Lenovo - moderator |
| 10.3.2.1 | MDT Enhancements | |
| R3-214865 | Propagation of user consent related information during Xn inter-PLMN handover | Huawei, Samsung |
| R3-214866 | (TPs for MDT BL CRs for TS 38.423, TS 37.320): User consent checking for MDT before UE context retrieval | Huawei |
| R3-215250 | Propagation of immediate MDT configuration in case of Xn inter-RAT HO | CATT |
| R3-215251 | Propagation of immediate MDT configuration in NG | CATT |
| R3-215452 | (TP for MDT BL CR for TS 38.413, TS 38.423) On improving the handling of user consent information | Ericsson |
| R3-215453 | (TP for MDT BL CR for TS 38.413, TS 38.423) Trace Failure Indication for cross RAT logged MDT configurations | Ericsson |
| R3-215754 | On demand SI of logged MDT | ZTE |
| R3-215755 | MDT leftover issue | ZTE |
| R3-215756 | [DRAFT] Reply LS on EN-DC related MDT configuration details | ZTE |
| R3-215757 | [DRAFT] Reply LS on propagation of user consent related information during Xn inter-PLMN handover | ZTE |
| R3-215858 | CB: # SONMDT9_MDTEnc - Summary of email discussion | Huawei - moderator |
| R3-215993 | Propagation of user consent related information during Xn inter-PLMN handover | Huawei, Samsung |
| R3-215994 | (TPs for MDT BL CRs for TS 38.423): User consent checking for MDT before UE context retrieval | Huawei |
| R3-215995 | (TPs for MDT BL CRs for TS 37.320): User consent checking for MDT before UE context retrieval | Huawei |
| R3-216019 | CB: # SONMDT9_MDTEnc - Summary of email discussion | Huawei - moderator |
| 10.3.2.2 | MDT for MR-DC | |
| R3-215316 | Further discussion on inter-node coordination for MDT in case of MR-DC | Nokia, Nokia Shanghai Bell |
| 10.5 | SON/MDT Optimizations for NR-U | |
| R3-214724 | Channel Status definitions used in NR-U channel occupancy | Charter Communications, Inc |
| R3-214725 | Signaling to request and report unlicensed channel occupancy | Charter Communications, Inc |
| R3-214815 | Discussion on the remaining “FFS” statements for MLB and MRO optimisation | Nokia, Nokia Shanghai Bell |
| R3-214867 | (TP for SON BLCR for TS 38.423): MLB and MRO for NR-U | Huawei |
| R3-215071 | Discussion on MRO for NR-U | CATT |
| R3-215299 | SON Enhancements for NR-U | Lenovo, Motorola Mobility |
| R3-215454 | Enabling L2 measurements to allow a UE to report LBT Monitoring Time | Ericsson |
| R3-215455 | Progressing on NR-U enhancements | Ericsson |
| R3-215522 | TP for SON BLCR for TS38.423: Support of SON for NR-U | Samsung |
| R3-215739 | Further Discussion on Load Balancing Optimization for NR-U | ZTE |
| R3-215859 | CB: # SONMDT10_NRU - Summary of email discussion | Ericsson - moderator |
| R3-216020 | CB: # SONMDT10_NRU - Summary of email discussion | Ericsson - moderator |
| R3-216042 | LS on NR-U channel information and procedures | Samsung |
| R3-216178 | CB: # SONMDT10_NRU - Summary of email discussion | Ericsson - moderator |
| 11.1 | General | |
| R3-215422 | WI work plan for RedCap | Ericsson |
| R3-215794 | LS on introducing NR RedCap Indication | SA2 |
| 11.2 | Support for RedCap Capability Exchange | |
| R3-214780 | Coordination of Redcap Capability across gNBs | Nokia, Nokia Shanghai Bell |
| R3-214895 | (TP for XnAP BL CR on RedCap) Xn mobility handling for RedCap Ues | Qualcomm Incorporated |
| R3-214940 | RedCap Capability Exchange between nodes | NEC |
| R3-215018 | Discussion on RedCap capability exchange | CATT |
| R3-215094 | Coordination between gNBs on the supporting of RedCap UEs | Huawei |
| R3-215159 | Redcap UE Capability Exchange and Support over Xn | RadiSys, Reliance JIO |
| R3-215497 | Discussion on Redcap UE Handover aspects and Capability exchange | RadiSys, Reliance JIO |
| R3-215554 | RedCap capability exchange | Samsung |
| R3-215679 | Discussion on coordination between gNBs for RedCap Ues | CMCC |
| R3-215788 | Response to R3-214940, R3-215018 | ZTE |
| R3-215860 | CB: # RedCap1_UECapability - Summary of email discussion | CMCC - moderator |
| R3-215917 | Redcap UE Capability Exchange and Support over Xn | RadiSys, Reliance JIO |
| 11.3 | Support for the Extended DRX enhancements for RedCap UEs | |
| R3-214712 | Reply LS on introducing extended DRX for RedCap UEs | SA2 |
| R3-214781 | Support of eDRX for Redcap UEs | Nokia, Nokia Shanghai Bell |
| R3-214782 | Support of eDRX for Redcap UEs | Nokia, Nokia Shanghai Bell |
| R3-214871 | Discussion on RAN3 support for RedCap | Samsung |
| R3-214872 | CR to TS38.473 for RedCap support | Samsung |
| R3-214896 | RedCap Open Issues in NGAP | Qualcomm Incorporated |
| R3-214897 | Introduction of RedCap UE support | Qualcomm Incorporated |
| R3-215019 | Discussion on extended DRX enhancements for RedCap UEs | CATT |
| R3-215020 | CR for support of RedCap UEs for 38.413 | CATT |
| R3-215092 | General Analysis of RedCap | Huawei |
| R3-215093 | Supporting RedCap UEs over NG interface | Huawei |
| R3-215095 | Supporting RedCap UEs over F1 interface | Huawei |
| R3-215104 | Discussion on introducing extended DRX for RedCap UEs | Huawei |
| R3-215157 | Redcap UE Support over F1 | RadiSys, Reliance JIO |
| R3-215423 | Discussion on SA2 LS for introducing eDRX for NR RedCap Ues | Ericsson |
| R3-215424 | Draft BL CR to NG-AP: Support of NR eDRX and RedCap early indication | Ericsson |
| R3-215425 | Draft BL CR to Xn-AP: Support of NR eDRX | Ericsson |
| R3-215426 | Draft BL CR to TS 38.300 on paging NR UE in RRC Inactive with eDRX | Ericsson |
| R3-215427 | Discussion on F1AP impacts related to NR RedCap | Ericsson |
| R3-215428 | Draft BL CR to F1-AP: Support of RedCap eDRX information | Ericsson |
| R3-215680 | Discussion on Extended DRX enhancements for RedCap UEs | CMCC |
| R3-215789 | Response to R3-215104 | ZTE |
| R3-215861 | CB: # RedCap2_eDRX - Summary of email discussion | Nokia - moderator |
| R3-215916 | Redcap UE Support over F1 | RadiSys, Reliance JIO |
| R3-216051 | Support for Redcap Ues | Nokia, Nokia Shanghai Bell |
| R3-216080 | Draft BL CR to TS 38.300 on RedCap UEs impacts to NG-RAN | Ericsson, Nokia, Nokia Shangahi Bell |
| R3-216108 | Support for Redcap Ues | Qualcomm Incorporated |
| R3-216115 | CR to TS38.473 for RedCap support | Samsung |
| R3-216117 | Support for Redcap Ues | Nokia, Nokia Shanghai Bell |
| R3-216118 | Support for Redcap Ues | Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-216119 | Draft BL CR to TS 38.300 on RedCap UEs impacts to NG-RAN | Ericsson, Nokia, Nokia Shangahi Bell, Samsung, CATT, Qualcomm Incorporated, ZTE |
| R3-216120 | BL CR to 38.401 Support for Redcap Ues | CATT |
| R3-216121 | BL CR to 38.470 Support for Redcap Ues | ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Samsung, CATT, Qualcomm Incorporated |
| R3-216122 | CB: # RedCap2_eDRX - Summary of email discussion | Nokia - moderator |
| 12.2 | Support for Carrier Selection and Carrier Specific Configuration | |
| R3-214738 | Discussion on Carrier Selection and Carrier Specific Configuration | ZTE |
| R3-214739 | Introduction of CEL based paging carrier selection | ZTE |
| R3-214783 | Support of Carrier Selection based on coverage level | Nokia, Nokia Shanghai Bell |
| R3-214784 | Support of Carrier Selection based on coverage level | Nokia, Nokia Shanghai Bell |
| R3-215004 | (TP to TS36.413) Consideration on Carrier Selection and Carrier Specific Configuration | Huawei |
| R3-215005 | Support of CE based carrier selection | Huawei |
| R3-215419 | Discussion on Rel-17 NB-IoT Carrier selection | Ericsson |
| R3-215897 | CB: # NBIoTMTC1_CarrierSelect - Summary of email discussion | Nokia - moderator |
| 12.3 | Others | |
| R3-215420 | Enhancement on Intra eNB CP Relocation for NB-IoT | Ericsson |
| R3-215898 | CB: # NBIoTMTC2_Others - Summary of email discussion | Ericsson - moderator |
| R3-216219 | CB: # NBIoTMTC2_Others - Summary of email discussion | Ericsson - moderator |
| 13.1 | General | |
| R3-214616 | BL CR to XnAP on Rel-17 eIAB | Samsung, Nokia, Nokia Shanghai Bell, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics |
| R3-214617 | CR on CP-UP separation for Rel-17 IAB | Nokia, Nokia Shanghai Bell, Samsung, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics |
| R3-214624 | CP-based Congestion Mitigation for IAB Network | ZTE |
| R3-214630 | CP-based Congestion Indication for IAB Networks | Ericsson |
| R3-214656 | BL CR to TS 38.401 on support of eIAB | Huawei |
| R3-214905 | Updated Workplan for Rel-17 IAB | Qualcomm Incorporated, Samsung (WI Rapporteurs) |
| R3-215899 | CB: # 1301_IAB_BL_CRs - Summary of email discussion | Qualcomm - moderator |
| R3-216061 | BL CR to TS 38.401 on support of eIAB | Huawei |
| R3-216260 | BL CR to TS 38.401 on support of eIAB | Huawei |
| R3-216261 | BL CR to XnAP on Rel-17 eIAB | Samsung, Nokia, Nokia Shanghai Bell, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics |
| R3-216262 | CP-based Congestion Indication for IAB Networks | Ericsson |
| R3-216286 | CP-based Congestion Indication for IAB Networks | Ericsson |
| 13.2.1.1 | Procedure Details | |
| R3-214677 | Reply LS on Inter-donor migration | RAN1 |
| R3-214690 | Reply LS on inter-donor migration | RAN2 |
| R3-214701 | Reply LS on inter-donor migration | RAN4 |
| R3-214822 | IAB Inter-Donor Topology Adaptation | Ericsson |
| R3-214869 | Procedure of full migration | Fujitsu |
| R3-214873 | (TP to BL CR of TS38.401) Discussion on inter-donor IAB node migration | Samsung |
| R3-214924 | Discussion on IAB inter-donor topology adaptation procedures | ZTE |
| R3-214930 | [Draft] Reply LS to RAN1 on inter-donor migration | ZTE |
| R3-214931 | [Draft] Reply LS to RAN2 on inter-donor migration | ZTE |
| R3-214953 | (TP for BL CR to 38.401) Inter-donor topology adaptation | Qualcomm Incorporated |
| R3-215013 | Discussion on inter-CU migration for IAB | CATT |
| R3-215302 | Discussion on IAB inter-donor migration | Lenovo, Motorola Mobility |
| R3-215344 | discussion on Inter-Donor IAB Node Migration | Nokia, Nokia Shanghai Bell |
| R3-215495 | Harmonized proposal on alternatives for full inter-donor IAB-node migration | AT&T |
| R3-215613 | (TP for NR_IAB_enh BL CR for TS 38.401) Inter-CU topology update | Huawei |
| R3-215749 | On Full Inter-Donor Migration in Rel-17 IAB | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-215900 | CB: # 1302_IAB_Inter_Donor_Mig - Summary of email discussion | Qualcomm - moderator |
| R3-216078 | CB: # 1302_IAB_Inter_Donor_Mig - Summary of email discussion | Qualcomm - moderator |
| 13.2.2 | Reduction of Service Interruption | |
| R3-214689 | Reply LS to RAN3 on reduction of service interruption during intra-donor IAB-node migration | RAN2 |
| R3-214823 | Reduction of Service Interruption in IAB Migration | Ericsson |
| R3-214874 | Discussion on service interruption reduction for Rel-17 IAB | Samsung |
| R3-214925 | Further considerations on service interruption reduction | ZTE |
| R3-214954 | Reduction of service interruption during IAB migration | Qualcomm Incorporated |
| R3-215014 | Discussion on reducation of service interruption | CATT |
| R3-215303 | Service interruption reduction for IAB migration | Lenovo, Motorola Mobility |
| R3-215345 | (TP for BL CR for TS 38.401) Discussion on Reduction of Service Interruption | Nokia, Nokia Shanghai Bell |
| R3-215612 | Reduction of Service Interruption for IAB topology update | Huawei |
| R3-215901 | CB: # 1303_IAB_Red_Serv_Inter - Summary of email discussion | Ericsson - moderator |
| R3-216090 | (TP for BL CR for TS 38.401) Discussion on Reduction of Service Interruption | Nokia, Nokia Shanghai Bell |
| 13.2.3 | Topology Redundancy | |
| R3-214824 | Inter-Donor Routing in IAB Topology Redundancy Scenarios | Ericsson |
| R3-214875 | (TP to BL CR of TS38.423) Discussion on inter-donor topology redundancy | Samsung |
| R3-214926 | Discussion on inter-donor topology redundancy | ZTE |
| R3-214955 | Inter-donor topology transport | Qualcomm Incorporated |
| R3-215015 | Discussion on inter-CU topology redundancy | CATT |
| R3-215304 | Discussion on IAB inter-donor topology redundancy | Lenovo, Motorola Mobility |
| R3-215346 | discussion on Inter-Donor IAB Topology Redundancy | Nokia, Nokia Shanghai Bell |
| R3-215611 | Inter-CU topology redundancy | Huawei |
| R3-215902 | CB: # 1304_IAB_Top_Red - Summary of email discussion | Huawei - moderator |
| R3-215920 | Inter-CU topology redundancy | Huawei |
| R3-216143 | CB: # 1304_IAB_Top_Red - Summary of email discussion | Huawei - moderator |
| 13.3.1 | Congestion Mitigation | |
| R3-214825 | (TP for IAB BL CR for TS 38.473) Congestion Mitigation in IAB Networks | Ericsson |
| R3-214929 | (TP for NR_IAB_enh BL CR for TS 38.473): Congestion indication in CP-based congestion mitigation | ZTE |
| R3-215008 | (TP for IAB BLCR 38.473) IAB Congestion Mitigation MPS exemption | Peraton Labs, CISA ECD, AT&T, Verizon |
| R3-215305 | (TP for IAB BL CR for TS 38.473) Remaining issues on congestion mitigation for IAB | Lenovo, Motorola Mobility |
| R3-215609 | Discussion on IAB congestion mitigation | Huawei |
| R3-215903 | CB: # 1305_IAB_Con_Mit - Summary of email discussion | Lenovo - moderator |
| R3-216041 | Discussion on IAB congestion mitigation | Huawei |
| R3-216184 | Discussion on IAB congestion mitigation | Huawei |
| R3-216186 | CB: # 1305_IAB_Con_Mit - Summary of email discussion | Lenovo - moderator |
| 13.3.2 | Multi-Hop Performance: QoS, Latency, Fairness | |
| R3-214681 | Reply LS on inter-donor-DU rerouting | RAN2 |
| R3-214826 | Uplink Inter-Donor Rerouting in IAB Networks | Ericsson |
| R3-214870 | IP-based tunneling between IAB-donor-DUs | Fujitsu |
| R3-214876 | (TP to BL CR of TS38.473) Discussion on the inter-donor-DU rerouting | Samsung |
| R3-214906 | Inter-donor-DU local rerouting for IAB | Qualcomm Incorporated |
| R3-214927 | Discussion on inter-Donor-DU re-routing in IAB | ZTE |
| R3-215016 | Discussion on inter-donor-DU re-routing | CATT |
| R3-215306 | Discussion on UL packet transmission for inter-donor-DU re-routing | Lenovo, Motorola Mobility |
| R3-215347 | (TP for BL CR for TS 38.401) Inter donor-DU re-routing | Nokia, Nokia Shanghai Bell |
| R3-215610 | Inter-donor re-routing for IAB and unnecessary transmission during topology update | Huawei |
| R3-215904 | CB: # 1306_IAB_Multi-hop - Summary of email discussion | ZTE - moderator |
| R3-216085 | CB: # 1306_IAB_Multi-hop - Summary of email discussion | ZTE - moderator |
| R3-216197 | CB: # 1306_IAB_Multi-hop - Summary of email discussion | ZTE - moderator |
| 13.4.1 | Resource Multiplexing of Child and Parent Links and CLI Management | |
| R3-214672 | Reply LS on IAB resource multiplexing | RAN1 |
| R3-214827 | Inter-Donor Resource Coordination in IAB Networks | Ericsson |
| R3-214928 | Discussion on resource multiplexing in IAB | ZTE |
| R3-215348 | Resource multiplexing | Nokia, Nokia Shanghai Bell |
| R3-215496 | Enhancements for IAB resource multiplexing | AT&T |
| R3-215608 | (TP for NR_IAB_enh BL CR for TS 38.423) IAB resource multiplexing | Huawei |
| R3-215614 | [Draft] LS on IAB resource multiplexing | ZTE |
| R3-215905 | CB: # 1307_IAB_Res_Multiplex - Summary of email discussion | Nokia - moderator |
| R3-216142 | (TP for NR_IAB_enh BL CR for TS 38.423) IAB resource multiplexing | Huawei |
| 14.1 | General | |
| R3-214631 | CPAC BL CR to TS 36.420 | China Telecommunications |
| R3-214640 | SCG BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-214641 | SCG BL CR to TS 37.340 | ZTE Corporation |
| R3-214642 | SCG BL CR to TS 38.401 | Huawei |
| R3-214643 | SCG BL CR to TS 38.423 | Ericsson |
| R3-214644 | SCG BL CR to TS 38.473 | Samsung |
| R3-214645 | CPAC BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-214646 | CPAC BL CR to TS 37.340 | Huawei |
| R3-214647 | CPAC BL CR to TS38.401 | ZTE |
| R3-214648 | CPAC BL CR to TS 38.423 | Ericsson |
| R3-214649 | CPAC BL CR to TS38.463 | Qualcomm |
| R3-214650 | BLCR to TS 38.473 for Conditional PScell Change/Addition | CATT |
| R3-215106 | (TP to 37.340 CPAC BL CR) Correction on MN initiated inter-SN CPC | Huawei |
| R3-215862 | CB: # MRDC1_BLCRs - Summary of email discussion | Huawei - moderator |
| R3-216242 | SCG BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-216243 | SCG BL CR to TS 37.340 | ZTE Corporation |
| R3-216244 | SCG BL CR to TS 38.401 | Huawei |
| R3-216245 | SCG BL CR to TS 38.423 | Ericsson |
| R3-216246 | SCG BL CR to TS 38.473 | Samsung |
| R3-216247 | CPAC BL CR to TS 36.420 | China Telecommunications |
| R3-216248 | CPAC BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-216249 | CPAC BL CR to TS 37.340 | Huawei |
| R3-216250 | CPAC BL CR to TS 38.423 | Ericsson |
| 14.2 | Signaling Support for Efficient Activation/Deactivation for One SCG and SCells | |
| R3-214765 | (TP for SCG BL CR to TS 37.340) Handling of network rejection for SCG (de)activation | Ericsson |
| R3-214766 | (TP for SCG BL CR to TS 38.423) Handling of network rejection for SCG (de)activation | Ericsson |
| R3-214807 | (TP to SCG BL CR to 38.423, LTE_NR_DC_enh2-Core) Completion of the solution for the SCG activation state change | Nokia, Nokia Shanghai Bell |
| R3-214808 | (TP to SCG BL CR to 36.423, LTE_NR_DC_enh2-Core) Completion of the solution for the SCG activation state change | Nokia, Nokia Shanghai Bell |
| R3-214877 | (TP to BL CR of TS38.401) Discussion on the SCG (de)activation | Samsung |
| R3-214878 | (TP to BL CR of TS38.473) Discussion on the SCG (de)activation | Samsung |
| R3-214941 | (TP for SCG BL CR to TS36.423) Acceptance / Rejection of SCG Activation / Deactivation | NEC |
| R3-214942 | Assisting information for SCG Activation / deactivation on E1 | NEC |
| R3-215006 | TP for SCG BL CR to TS38.423 36.423 38.463 | ZTE |
| R3-215007 | TP for SCG BL CR to TS 38.473 | ZTE |
| R3-215107 | (TP to 38.401 SCG BL CR) SCG activation and deactivation | Huawei |
| R3-215108 | (TPs to 38.463 38.425 SCG BL CR) SCG activation and deactivation | Huawei |
| R3-215111 | Discussion on efficient Activation/Deactivation for SCG | CATT |
| R3-215112 | (TP for SCG BLCR for TS 38423)efficient Activation/Deactivation for SCG | CATT |
| R3-215325 | Left issues on SCG activation and deactivation | Lenovo, Motorola Mobility |
| R3-215326 | Discussion on SCG activation and deactivation impact on E1 interface | Lenovo, Motorola Mobility, ZTE, NEC, Samsung |
| R3-215327 | Support of SCG Activation and Deactivation | Lenovo, Motorola Mobility |
| R3-215863 | CB: # MRDC2_SCGActivation_Deactivation - Summary of email discussion | ZTE - moderator |
| R3-215951 | CB: # MRDC2_SCGActivation_Deactivation - Summary of email discussion | ZTE - moderator |
| R3-216037 | (TP to 38.401 SCG BL CR) SCG activation and deactivation | Huawei |
| R3-216084 | TP for SCG BL CR to TS38.423 | ZTE |
| R3-216101 | (TP for SCG BL CR to TS 37.340) Handling of network rejection for SCG (de)activation | Ericsson |
| R3-216102 | (TP to SCG BL CR to 36.423, LTE_NR_DC_enh2-Core) Completion of the solution for the SCG activation state change | Nokia, Nokia Shanghai Bell |
| R3-216103 | (TP to BL CR of TS38.473) Discussion on the SCG (de)activation | Samsung |
| 14.3 | Signaling Support for Conditional PSCell Change/Addition | |
| R3-214697 | Reply LS on Conditional PSCell Addition/Change agreements | RAN2 |
| R3-214747 | (TP for CPAC BLCR to TS36.423) Reusing X2AP Data Forwarding Address Indication procedure for Early data forwarding | ZTE, Qualcomm Incorporated, Lenovo, Ericsson |
| R3-214748 | (TP for CPAC BL CR to TS 37.340) Remaining issues for MN initiated CPC | ZTE |
| R3-214749 | (TP for CPAC BLCR to TS36.423/TS38.423) CPA and CPC replace and cancel | ZTE |
| R3-214767 | (TP for CPAC BL CR to TS 38.423) Inter-node message and Support of SN-initiated CPC | Ericsson |
| R3-214768 | (TP for CPAC BL CR to TS 38.423) CPC/CPA Cancellation | Ericsson |
| R3-214809 | (TP to CPAC BL CR to 38.423, LTE_NR_DC_enh2-Core) Max number of PSCells, cancellation and modification of a CPAC | Nokia, Nokia Shanghai Bell |
| R3-214810 | (TP to CPAC BL CR to 36.423, LTE_NR_DC_enh2-Core) Max number of PSCells, cancellation and modification of a CPAC | Nokia, Nokia Shanghai Bell |
| R3-214842 | (TP for CPAC BLCR to TS36.423) Resolve the overload issues in CPAC procedure | China Telecommunication |
| R3-214843 | (TP for CPAC BLCR to TS38.423) Resolve the overload issues in CPAC procedure | China Telecommunication |
| R3-214920 | CPAC replace procedures | Qualcomm Incorporated |
| R3-214921 | SN initiated Inter-SN CPC procedure | Qualcomm Incorporated |
| R3-214943 | (TP for CPAC BL CR to TS 36.423 ) On CPAC (Conditional PSCell Addition and PSCell Change) | NEC |
| R3-214944 | (TP for CPAC BL CR to TS 38.423 ) On CPAC (Conditional PSCell Addition and PSCell Change) | NEC |
| R3-215010 | Remaining issues on SN initiated conditional PSCell change | NTT DOCOMO INC. |
| R3-215109 | (TP to 37.340 CPAC BL CR) Support of inter-SN CPC | Huawei |
| R3-215110 | (TPs to 38.423 36.423 38.473 38.425 CPAC BL CRs) PDCP PDU forwarding and discard | Huawei |
| R3-215113 | Further Considerations on Conditional PSCell ChangeAddition | CATT |
| R3-215114 | (TP for CPAC BLCR for TS 38473)Conditional PScell Change/Addition | CATT |
| R3-215301 | (TP for CPAC BL CR to TS 38.423) CPAC Cancel | Samsung |
| R3-215307 | (TP for CPAC BL CR to TS 36.423) CPAC Cancel | Samsung |
| R3-215328 | Left issues on CPAC | Lenovo, Motorola Mobility |
| R3-215527 | Open issues on CPAC replace and cancel | LG Electronics |
| R3-215623 | (TP to CPAC BLCR to 37.340) Coordination information | Google Inc. |
| R3-215751 | (TP to CPAC BLCR to 37.340) SN Release after Inter-SN CPC | Google Inc. |
| R3-215764 | (TP for [LTE_NR_DC_enh2-Core] CPAC BLCR for TS 36423) Conditional PSCell Change/Addition | CICT |
| R3-215864 | CB: # MRDC3_CPAC - Summary of email discussion | Lenovo - moderator |
| R3-215952 | CB: # MRDC3_CPAC - Summary of email discussion | Lenovo - moderator |
| R3-216038 | (TP to 37.340 CPAC BL CR) Updates of CPAC related procedures | Huawei |
| R3-216147 | (TP for CPAC BL CR to TS 38.423) CPC/CPA Cancellation | Ericsson |
| R3-216148 | (TP for CPAC BLCR to TS36.423) CPA and CPC replace and cancel | ZTE |
| R3-216149 | (TP for 38.420 CPAC BL CR) CPC cancel | Lenovo |
| R3-216167 | (TP for 36.420 CPAC BL CR) CPC cancel | China Telecom |
| R3-216207 | CPAC BL CR to TS 38.420 | Lenovo, Motorola Mobility |
| 15.1 | General | |
| R3-214633 | CR to 38.413 on Introduction of QoE measurement | Huawei, China Mobile, China Unicom, Ericsson, Samsung |
| R3-214634 | BLCR to 38.300 | China Unicom, Ericsson, ZTE |
| R3-214769 | BLCR to 38.410: Support of QoE Measurement Collection for NR | Nokia, Nokia Shanghai Bell |
| R3-215703 | Updated Workplan for Rel-17 NR QoE | China Unicom, Ericsson |
| R3-215865 | CB: # QoE1_Workplan - Summary of email discussion | China Unicom - moderator |
| R3-216272 | BLCR to 38.300 | China Unicom, Ericsson, ZTE |
| R3-216273 | BLCR to 38.410: Support of QoE Measurement Collection for NR | Nokia, Nokia Shanghai Bell |
| R3-216279 | CR to 38.413 on Introduction of QoE measurement | Huawei, China Mobile, China Unicom, Ericsson, Samsung |
| 15.2.1.1 | Configuration, Activation and Deactivation Procedures | |
| R3-214717 | LS Reply on requirement for configuration changes of ongoing QMC sessions | SA4 |
| R3-214720 | Reply LS on (de)activation and failure handling of NR QMC | SA5 |
| R3-214726 | Procedures for Configuration, Activation and Deactivation of QMC | Ericsson |
| R3-214907 | QoE Configuration, Activation and Deactivation Procedures | Qualcomm Incorporated |
| R3-214981 | [DRAFT] LS Reply on requirement for configuration changes of ongoing QMC sessions | Ericsson |
| R3-215115 | Discussion on NR QoE configuration procedures | CATT |
| R3-215308 | (TP for BL CR to TS 38.300) Stage 2 updates following replies from other WGs | Nokia, Nokia Shanghai Bell |
| R3-215309 | (TP for BL CR to TS 38.410) QMC function definition | Nokia, Nokia Shanghai Bell |
| R3-215543 | NR QoE Activation and Deactivation Procedures | Samsung |
| R3-215631 | Discussion on QoE activation and deactivation procedures | ZTE, China Telecom, China Unicom |
| R3-215866 | CB: # QoE2_Activation_Deactivation - Summary of email discussion | ZTE - moderator |
| R3-216104 | Stage 2 TP to 38.300 BL CR on QoE | ZTE, Huawei, Nokia |
| R3-216113 | (TP for BL CR to TS 38.410) QMC function definition | Nokia, Nokia Shanghai Bell |
| R3-216150 | Stage 2 TP to 38.300 BL CR on QoE | ZTE, Huawei, Nokia, Ericsson, Qualcomm, Samsung |
| 15.2.1.2 | Configuration Details | |
| R3-214694 | QoE Reference and maximum number of QoE configurations in RRC | RAN2 |
| R3-214704 | Reply LS on the mapping between service types and slice at application | SA2 |
| R3-214716 | Reply LS on the mapping between service types and slice at application | SA4 |
| R3-214727 | (TP for QoE BL CR for TS 38.413) QoE Configuration and Reporting | Ericsson |
| R3-214908 | QoE configuration details | Qualcomm Incorporated |
| R3-214909 | Per slice QoE | Qualcomm Incorporated |
| R3-214979 | [DRAFT] LS Reply on QoE Reference and Maximum Number of QoE Configurations in RRC | Ericsson |
| R3-214980 | [DRAFT] Reply LS on Mapping Between Service Types and Slice at Application | Ericsson |
| R3-215021 | Distribution of QMC Job Attributes for Management Based QoE | Ericsson, CMCC, China Unicom |
| R3-215116 | Introduction of NR QoE measurements on Xn interface | CATT |
| R3-215117 | Discussion on NR QoE configuration details | CATT |
| R3-215310 | Stage 3 updates following replies from other WGs | Nokia, Nokia Shanghai Bell |
| R3-215544 | NR QoE Configuration Details | Samsung |
| R3-215633 | Discussion on NR QoE Configuration | ZTE, China Telecom, China Unicom |
| R3-215635 | (TP for BL CR of TS 38.413) NR QoE Configuration | ZTE, China Telecom |
| R3-215637 | (TP for BL CR of TS 38.423) NR QoE Configuration | ZTE, China Telecom |
| R3-215657 | Further discussions on configuration details | Huawei |
| R3-215658 | TP to 38.413 on configuration details | Huawei |
| R3-215663 | Stage 2 TPs to 38.300 on RAN related measurements and information | Huawei |
| R3-215689 | Remaining open issues on per-slice QoE measurement | CMCC |
| R3-215704 | Clarification for QoE modification and overriding | China Unicom |
| R3-215706 | Per-slice QoE measurement configuration and reporting | China Unicom |
| R3-215708 | QoE Configuration and Reporting | China Unicom |
| R3-215867 | CB: # QoE3_Configuration_Report - Summary of email discussion | Huawei - moderator |
| R3-216106 | TP to 38.413 on configuration details | Huawei |
| R3-216141 | Support of including slice ID in the QoE reporting container | Huawei |
| R3-216201 | Support of including slice ID in the QoE reporting container | Huawei |
| R3-216202 | TP to 38.413 on configuration details | Huawei |
| R3-216225 | Support of including slice ID in the QoE reporting container | Huawei |
| 15.2.2 | Measurement Collection and Continuity in Intra-System Intra-RAT Mobility | |
| R3-214728 | Mobility Support for NR QoE Management | Ericsson |
| R3-214729 | CR TS 38.423 Mobility Support for NR QoE Measurement Collection | Ericsson |
| R3-214910 | QoE measurement collection and reporting continuity in mobility scenarios | Qualcomm Incorporated |
| R3-215118 | Discussion on Measurement Collection and Continuity in Intra-System Intra-RAT Mobility | CATT |
| R3-215311 | Inter-node propagation of management-based QMC configuration | Nokia, Nokia Shanghai Bell |
| R3-215545 | Mobility issues of NR QoE | Samsung |
| R3-215639 | Further discussion on Measurement Collection and Continuity in Intra-System Intra-RAT Mobility | ZTE, China Telecom |
| R3-215662 | Further discussions on measurement collection and mobility continuity | Huawei |
| R3-215868 | CB: # QoE4_Mobility - Summary of email discussion | Ericsson - moderator |
| R3-216072 | CR TS 38.423 Mobility Support for NR QoE Measurement Collection | Ericsson |
| R3-216116 | CB: # QoE4_Mobility - Summary of email discussion | Ericsson - moderator |
| R3-216205 | CB: # QoE4_Mobility - Summary of email discussion | Ericsson - moderator |
| R3-216206 | CR TS 38.423 Mobility Support for NR QoE Measurement Collection | Ericsson |
| R3-216226 | CR TS 38.423 Mobility Support for NR QoE Measurement Collection | Ericsson |
| R3-216231 | LS to SA5 on management based QoE mobility | ZTE |
| 15.3 | Support for RAN-Visible QoE | |
| R3-214730 | RAN Visible QoE Metrics | Ericsson |
| R3-214731 | Configuration and Reporting of RAN Visible QoE | Ericsson |
| R3-214911 | RAN Visible QoE | Qualcomm Incorporated |
| R3-215119 | Discussion on RAN visible QoE configuration and reporting | CATT |
| R3-215120 | TP for 38.423 on RAN visible QoE configuration and reporting | CATT |
| R3-215312 | Handling of open points for RAN visible QoE | Nokia, Nokia Shanghai Bell |
| R3-215546 | RAN visible QoE | Samsung |
| R3-215547 | (CR for TS38.473) Support of QoE information transfer | Samsung |
| R3-215641 | Discussion on configuration and reporting of RVQoE | ZTE, China Telecom |
| R3-215644 | Consideration on RAN visible QoE | ZTE, China Telecom |
| R3-215647 | [draft] LS on the support for RAN visible QoE | ZTE, China Telecom |
| R3-215659 | Further discussions on RAN visible QoE metrics | Huawei |
| R3-215660 | Draft LS on RAN visible QoE conclusions | Huawei |
| R3-215869 | CB: # QoE5_RANVisible - Summary of email discussion | Qualcomm - moderator |
| R3-216040 | (CR for TS38.473) Support of QoE information transfer | Samsung |
| R3-216135 | [Draft] Support for RAN visible QoE metrics | Ericsson |
| R3-216136 | [Draft] Support for RAN visible QoE measurements | Ericsson |
| R3-216137 | CB: # QoE5_RANVisible - Summary of email discussion | Qualcomm - moderator |
| R3-216138 | LS on RAN3 agreements for RAN visible QoE | Qualcomm Incorporated |
| R3-216144 | (BL CR for TS38.473) Support of QoE information transfer | Samsung |
| R3-216227 | LS on RAN3 agreements for RAN visible QoE | Qualcomm Incorporated |
| 15.4 | Alignment of Radio-Related Measurement and QoE Measurements | |
| R3-214732 | The Alignment of Radio-Related Measurements and QoE Measurements | Ericsson |
| R3-214912 | Alignment of Radio-Related Measurement and QoE Measurements | Qualcomm Incorporated |
| R3-215121 | Discussion on Alignment of MDT and QoE Measurements | CATT |
| R3-215313 | Remaining open issues for alignment of radio-related measurements and QoE measurements | Nokia, Nokia Shanghai Bell |
| R3-215548 | Alignment of MDT and QoE | Samsung |
| R3-215661 | Further discussions on RAN related measurements and informaiton | Huawei |
| R3-215667 | Further discussion on alignment of MDT and QoE Measurements | ZTE, China Telecom, China Unicom |
| R3-215668 | (TP for 38.401) Alignment of MDT and QoE Measurements | ZTE, China Telecom, China Unicom |
| R3-215669 | (TP for E1/F1) Alignment of Radio-Related Measurement and QoE Measurements | ZTE, China Telecom |
| R3-215688 | Remaining open issues on alignment of radio related measurement and QoE measurement | CMCC |
| R3-215870 | CB: # QoE6_MDTAlignment - Summary of email discussion | Nokia - moderator |
| R3-216105 | (TP for E1/F1) Alignment of Radio-Related Measurement and QoE Measurements | ZTE, China Telecom |
| R3-216179 | CB: # QoE6_MDTAlignment - Summary of email discussion | Nokia - moderator |
| 16.1 | General | |
| R3-214651 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-214652 | Introduction of support for eNPN | Qualcomm Incorporated |
| R3-214653 | Supporting enhanced private network | Huawei |
| R3-214833 | Work Plan for Enhancement for Private Network Support for NG-RAN WI | China Telecommunication |
| R3-215906 | CB: # NPN1_Workplan_BLCRs - Summary of email discussion | China Telecom - moderator |
| R3-216251 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-216252 | Supporting enhanced private network | Huawei |
| 16.2.1 | Cell Access Control | |
| R3-214708 | Reply to LS on clarifications on eNPN features | SA2 |
| R3-214785 | (TP for TS 38.300) Support for Onboarding stage 2 | Nokia, Nokia Shanghai Bell |
| R3-214786 | (TP for TS 38.413) Support for Onboarding stage 3 | Nokia, Nokia Shanghai Bell |
| R3-214834 | (TP for TS 38.413) Support for eNPN | China Telecommunication |
| R3-214835 | (TP for TS 38.300) Support for eNPN | China Telecommunication |
| R3-214898 | (TP for BL CR for 38.413) Open issues for eNPN | Qualcomm Incorporated |
| R3-214899 | (TP for BL CR for 38.300) Open issues for eNPN | Qualcomm Incorporated |
| R3-215017 | Discussion on cell access control for NPN | CATT |
| R3-215134 | (TP for NG_RAN_PRN_enh BLCR for TS 38.413) Supporting enhanced private network | Huawei |
| R3-215135 | Supporting enhanced private network | Huawei |
| R3-215200 | Cell access control for SNPN access using external credentials | Ericsson |
| R3-215201 | Cell access control for UE onboarding | Ericsson |
| R3-215630 | Left issues on enhanced NPN | ZTE Corporation |
| R3-215632 | TP for TS38.300 on enhanced NPN | ZTE Corporation |
| R3-215713 | Discussion on support of onboarding over NG | LG Electronics |
| R3-215714 | (TP for eNPN BL CR for TS 38.413) Support of onboarding over NG | LG Electronics |
| R3-215907 | CB: # NPN2_CellAccessControl - Summary of email discussion | Nokia - moderator |
| R3-215968 | (TP for TS 38.300) Support for Onboarding stage 2 | Nokia, Nokia Shanghai Bell |
| R3-215969 | (TP for TS 38.413) Support for Onboarding stage 3 | Nokia, Nokia Shanghai Bell |
| R3-215983 | (TP for TS 38.413) Support for Onboarding stage 3 | Nokia, Nokia Shanghai Bell |
| R3-216014 | CB: # NPN2_CellAccessControl - Summary of email discussion | Nokia - moderator |
| R3-216021 | (TP for TS 38.413) Support for Onboarding stage 3 | Nokia, Nokia Shanghai Bell |
| 17.1 | General | |
| R3-215690 | Updated work plan for RAN slicing | CMCC, ZTE |
| R3-215797 | Reply LS on Slice list and priority information for cell reselection | SA2 |
| R3-215873 | CB: # RANSlicing1_Workplan_LSin - Summary of email discussion | CMCC - moderator |
| 17.2 | Support Service Continuity | |
| R3-214817 | Handling of Slicing resource shortage | Nokia, Nokia Shanghai Bell |
| R3-214818 | Handling of Slice Resource Shortage | Nokia, Nokia Shanghai Bell |
| R3-215129 | Discussion on Support Service Continuity | CATT |
| R3-215224 | Analysis of service continuity scenarios for network slicing | Ericsson |
| R3-215226 | LS on RRM Policy utilisation monitoring and reconfiguration | Ericsson |
| R3-215252 | Supporting network slicing enhancement | Huawei |
| R3-215541 | Discussion on Support Service Continuity | Samsung |
| R3-215691 | Solutions to support service continuity | CMCC |
| R3-215692 | BLCR 38.300 on enhancement of RAN slicing | CMCC |
| R3-215758 | Support service continuity | ZTE |
| R3-215874 | CB: # RANSlicing2_Service_Continuity - Summary of email discussion | Nokia - moderator |
| R3-215949 | Handling of Slice Resource Shortage | Nokia, Nokia Shanghai Bell |
| R3-215950 | Clarification of SCG outside RA for slicing | Nokia, Nokia Shanghai Bell |
| R3-215958 | LS on RRM Policy utilisation monitoring and reconfiguration | Ericsson |
| R3-215959 | CB: # RANSlicing2_Service_Continuity - Summary of email discussion | Nokia - moderator |
| R3-215966 | Handling of Slice Resource Shortage | Nokia, Nokia Shanghai Bell |
| R3-215967 | LS on Clarification of SCG outside RA for slicing | Nokia, Nokia Shanghai Bell |
| R3-216237 | LS on Clarification of SCG outside RA for slicing | Nokia, Nokia Shanghai Bell |
| R3-216238 | LS on RRM Policy utilisation monitoring and reconfiguration | Ericsson |
| 17.3 | Support the Enforcement of Slice MBR | |
| R3-214819 | Introduction of UE Slice MBR | Nokia, Nokia Shanghai Bell |
| R3-215127 | Discussion on Supporting for UE-Slice-MBR | CATT |
| R3-215128 | CR to 38.413 for Enhancement of RAN Slicing | CATT |
| R3-215225 | Analysis of Solutions for S-MBR support | Ericsson |
| R3-215253 | Supporting network slicing enhancement | Huawei |
| R3-215254 | Supporting network slicing enhancement | Huawei |
| R3-215542 | Discussion on Slice MBR | Samsung |
| R3-215759 | Impact on RAN slicing of UE slice MBR | ZTE |
| R3-215760 | Impact on RAN slicing of Target NSSAI | ZTE |
| R3-215780 | Support of Target NSSAI for UE redirection | LG Electronics |
| R3-215875 | CB: # RANSlicing3_UESliceMBR - Summary of email discussion | ZTE - moderator |
| R3-215960 | CB: # RANSlicing3_UESliceMBR - Summary of email discussion | ZTE - moderator |
| R3-216053 | Supporting network slicing enhancement | Huawei |
| 18.1 | General | |
| R3-215705 | TR 37.817 v0.3.0 | CMCC |
| R3-215847 | Work plan for Study on enhancement for data collection for NR and EN-DC | CMCC |
| R3-216278 | TR 37.817 v0.4.0 | CMCC |
| 18.2 | High-Level Principles and Definitions | |
| R3-214733 | RAN Intelligence Framework – Further Discussion on Model Testing and Model Performance Evaluation | Futurewei |
| R3-214796 | Discussion on open issues within AI/ML-based functional framework for RAN intelligence | Deutsche Telekom |
| R3-214951 | Proposed resolutions to open issues on functional framework | NEC |
| R3-215055 | Discussion on the model performance feedback arrow | CATT |
| R3-215237 | (TP for SON BL CR for TR 37.817) Framework for RAN intelligence | Ericsson |
| R3-215244 | Model management in AI/ML framework | Qualcomm Incorporated |
| R3-215268 | High level principle and Functional Framework of AI/ML enabled NG-RAN Network | Intel Corporation |
| R3-215330 | Remaining issues on AI functional framework | Lenovo, Motorola Mobility |
| R3-215464 | Architecture for RAN AI/ML | Deutsche Telekom, Qualcomm Incorporated, T-Mobile USA |
| R3-215477 | (TP for TR 37.817) Open points on AI/ML Framework and Data Collection Discussions | Nokia, Nokia Shanghai Bell |
| R3-215523 | Further discussion on AI Functional Framework for RAN intelligence | ZTE Corporation, China Unicom |
| R3-215561 | Discussion on Functional Framework and High-Level Principles | Samsung, Verizon Wireless |
| R3-215664 | Further discussions on remaining open issues about general principles and frame work | Huawei |
| R3-215694 | Remaining aspect of AI framework | CMCC |
| R3-215908 | CB: # AIRAN1_Framework - Summary of email discussion | Deutsche Telekom - moderator |
| R3-216112 | TP for TR 37.817 on General Framework | Deutsche Telekom |
| R3-216123 | TP for TR 37.817 on General Framework | Deutsche Telekom |
| R3-216192 | TP for TR 37.817 on General Framework | Deutsche Telekom |
| 18.4.1 | Network Energy Saving | |
| R3-215072 | Discussion on Standards Impact on energy saving | CATT |
| R3-215216 | Network Energy Saving | Ericsson |
| R3-215245 | UE assistance information for AI/ML | Qualcomm Incorporated |
| R3-215269 | AI/ML based network energy saving and load balancing | Intel Corporation |
| R3-215473 | Network Energy Saving – Solutions and Standard Impacts | Futurewei |
| R3-215524 | Further discussion on solution to AI-based Energy Saving | ZTE Corporation, Lenovo, Motorola Mobility, China Unicom |
| R3-215562 | Discussion on Standard Impact for AI/ML based Network Energy Saving | Samsung, Verizon Wireless |
| R3-215665 | (TP to TR 37.817) Remaining issues for AI based Energy Saving | Huawei |
| R3-215707 | Solutions of AI based ES for Split Architecture Base Station | China Telecomunication Corp. |
| R3-215785 | TP to TR 37.817 on standard impacts for AI-based ES use case | China Telecomunication Corp. |
| R3-215909 | CB: # AIRAN2_ES - Summary of email discussion | ZTE - moderator |
| R3-216107 | Further discussion on solution to AI-based Energy Saving | ZTE Corporation, Lenovo, Motorola Mobility, China Unicom |
| R3-216214 | CB: # AIRAN2_ES - Summary of email discussion | ZTE - moderator |
| R3-216215 | Further discussion on solution to AI-based Energy Saving | ZTE Corporation, Lenovo, Motorola Mobility, China Unicom |
| R3-216228 | Further discussion on solution to AI-based Energy Saving | ZTE Corporation, Lenovo, Motorola Mobility, China Unicom |
| 18.4.2 | Load Balancing | |
| R3-214734 | AI/ML-based Load Balancing – Discussion on Solutions and Standards Impact | Futurewei |
| R3-214952 | Discussion on Load Balancing Solutions and Standard Impact | NEC |
| R3-215073 | Discussion on Standards Impact on load balancing | CATT |
| R3-215246 | RAN data collection enhancement for AI/ML | Qualcomm Incorporated |
| R3-215331 | Discussion on traffic load prediction | Lenovo, Motorola Mobility |
| R3-215474 | AI/ML Load Balancing and Mobility Optimization use cases | Ericsson |
| R3-215478 | (TP for TR 37.817) Further Discussion on Standard Impacts of AI/ML Load Balancing | Nokia, Nokia Shanghai Bell |
| R3-215525 | Further discussion on solution to AI-based load balancing | ZTE Corporation, China Unicom |
| R3-215666 | (TP to TR 37.817) Remaining issues for AI based mobility enhancements and load balancing | Huawei |
| R3-215698 | Remaining issues for AI based Load balancing | CMCC |
| R3-215910 | CB: # AIRAN3_LB - Summary of email discussion | Ericsson - moderator |
| R3-216114 | AI/ML Load Balancing use case description | Ericsson |
| R3-216224 | AI/ML Load Balancing use case description | Ericsson |
| R3-216230 | AI/ML Load Balancing use case description | Ericsson |
| 18.4.3 | Mobility Optimization | |
| R3-214816 | Correction of Mobility Optimization - Solutions and standards impacts | InterDigital |
| R3-215056 | Discussion on Standards Impact on Mobility | CATT |
| R3-215130 | Further discussion on use case of mobility optimization | Purple Mountain Laboratories |
| R3-215270 | AI/ML based mobility optimization | Intel Corporation |
| R3-215332 | Discussion on standard impact to support mobility optimization | Lenovo, Motorola Mobility |
| R3-215479 | (TP for TR 37.817) Further Discussion on Standard Impacts of AI/ML Mobility Optimization | Nokia, Nokia Shanghai Bell |
| R3-215526 | Further discussion on solution to AI-based mobility optimization | ZTE Corporation, China Unicom |
| R3-215528 | Input/output information for support of AI/ML enabled Mobility Optimization | LG Electronics |
| R3-215563 | Discussion on Standard Impact for AI/ML based Mobility Optimization | Samsung, Verizon Wireless |
| R3-215699 | Remaining issues for AI based Mobility and Energy Saving | CMCC |
| R3-215911 | CB: # AIRAN3_Mobility - Summary of email discussion | CATT - moderator |
| R3-216100 | (TP for TR 37.817) AI/ML based mobility optimization | CATT |
| R3-216198 | CB: # AIRAN3_Mobility - Summary of email discussion | CATT - moderator |
| R3-216199 | (TP for TR 37.817) AI/ML based mobility optimization | CATT |
| R3-216232 | (TP for TR 37.817) AI/ML based mobility optimization | CATT |
| 19.1 | General | |
| R3-214635 | BL CR to 38.473 | Huawei |
| R3-214665 | Introduction of NR Positioning enhancements to NRPPa | Ericsson |
| R3-216270 | Introduction of NR Positioning enhancements to NRPPa | Ericsson |
| R3-216271 | BL CR to 38.473 | Huawei |
| 19.2.1 | Positioning Accuracy Improvements | |
| R3-214977 | (TP for NR_pos_enh BL CR for TS 38.455) Resolution of open issues for UL AoA | Nokia, Nokia Shanghai Bell |
| R3-215390 | (TP for POS BL CR for TS 38.455, TS 38.473) on positioning enhancement | Huawei |
| R3-215605 | Further Consideration of UL-AOAZOA Assistance Information | CATT |
| R3-215646 | Discussion on supporting UL-AoA positioning measurements with gNB ARP | ZTE Corporation |
| R3-215648 | TP for TS38.455 on supporting UL-AoA positioning measurements with gNB ARP | ZTE Corporation |
| R3-215682 | (TP for TS 38.455) Positioning Accuracy Improvements | CMCC |
| R3-215876 | CB: # 1901_Pos_Acc_Imp - Summary of email discussion | Nokia - moderator |
| R3-216034 | (TP for NR_pos_enh BL CR for TS 38.455) Resolution of open issues for UL AoA | Nokia, Nokia Shanghai Bell |
| R3-216054 | (TP for POS BL CR for TS 38.473) on UL AoA | Huawei |
| R3-216062 | (TP for NR_pos_enh BL CR for TS 38.473) Resolution of open issues for UL AoA | Nokia, Nokia Shanghai Bell |
| R3-216068 | (TP for NR_pos_enh BL CR for TS 38.455) Resolution of open issues for UL AoA | Nokia, Nokia Shanghai Bell |
| 19.2.2 | RRC_INACTIVE State Positioning | |
| R3-215391 | (TP for POS BL CR for TS 38.423, TS 38.455, TS 38.473) Discussion on RRC Inactive positioning | Huawei |
| R3-215438 | Discussion on support of RRC-Inactive Positioning | Ericsson |
| R3-215439 | Addition of positioning measurements over Xn | Ericsson |
| R3-215440 | TP to F1AP BL CR: Mirror impacts to NRPPa | Ericsson |
| R3-215553 | Positioning in RRC inactive state | Samsung |
| R3-215606 | Positioning for UEs in RRC_INACTIVE state | CATT |
| R3-215681 | Discussion on RRC INACTIVE State Positioning | CMCC |
| R3-215849 | Response to R3-215391, R3-215438 | Samsung Electronics Iberia SA |
| R3-215877 | CB: # 1902_Pos_RRC_INACTIVE - Summary of email discussion | Ericsson - moderator |
| R3-216002 | TP to NRPPa BL CR: addition of cause value | Ericsson |
| R3-216058 | TP to F1AP BL CR: Mirror impacts to NRPPa | Ericsson |
| R3-216077 | CB: # 1902_Pos_RRC_INACTIVE - Summary of email discussion | Ericsson - moderator |
| R3-216082 | TP to NRPPa BL CR: addition of cause value | Ericsson |
| 19.2.3 | On-Demand PRS Transmission and Reception | |
| R3-214978 | (TP for NR_pos_enh BL CR for TS 38.455) Further details for on-demand PRS | Nokia, Nokia Shanghai Bell |
| R3-215392 | Discussion and Draft LS on on-demand PRS | Huawei |
| R3-215607 | Discussion on on-demand PRS | CATT |
| R3-215878 | CB: # 1903_Pos_OnDemandPRS - Summary of email discussion | CATT - moderator |
| R3-216035 | (TP for NR_pos_enh BL CR for TS 38.455) Further details for on-demand PRS | Nokia, Nokia Shanghai Bell |
| R3-216091 | CB: # 1903_Pos_OnDemandPRS - Summary of email discussion | CATT - moderator |
| 19.3 | Support for Latency Improvement | |
| R3-215393 | (TP for POS BL CR for TS 38.455, TS 38.473): Latency improvement in positioning | Huawei |
| R3-215441 | Discussion on latency improvements for Rel-17 positioning | Ericsson |
| R3-215879 | CB: # 1904_Pos_LatencyImprovement - Summary of email discussion | Huawei - moderator |
| R3-216029 | (TP for POS BL CR for TS 38.455) Latency improvement in positioning | Huawei |
| R3-216030 | (TP for POS BL CR for TS 38.473): Latency improvement in positioning | Huawei |
| R3-216129 | CB: # 1904_Pos_LatencyImprovement - Summary of email discussion | Huawei - moderator |
| R3-216130 | (TP for POS BL CR for TS 38.455) Latency improvement in positioning | Huawei |
| R3-216131 | (TP for POS BL CR for TS 38.473): Latency improvement in positioning | Huawei |
| R3-216132 | (TP for Pos BL CR TS 38.455) Measurement Amount IE | Huawei |
| R3-216133 | (TP for Pos BL CR TS 38.473) Measurement Amount IE | Huawei |
| 20.1 | General | |
| R3-214614 | Clarification of NAS Node Selection Function for NTN nodes providing access over multiple countries | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei |
| R3-214615 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-214663 | Support Non-Terrestrial Networks | Huawei, Thales, Ericsson, ZTE, Qualcomm Incorporated |
| R3-214664 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-215099 | (TP for BL CR TS 38.300) NTN Stage 2 Update | Huawei |
| R3-215100 | (TP for BL CR TS 38.413) stage 3 TP for mapped CGIs | Huawei |
| R3-215880 | CB: # 2001_NTN_General - Summary of email discussion | Thales - moderator |
| R3-216036 | (TP for BL CR TS 38.300) NTN Stage 2 Update | Huawei |
| R3-216269 | Support Non-Terrestrial Networks | Huawei, Thales, Ericsson, ZTE, Qualcomm Incorporated |
| 20.2.1 | Network Identifier Handling | |
| R3-214682 | Response LS on Multiple TACs per PLMN | RAN2 |
| R3-214688 | Response LS on storage of UE Positioning Capabilities | RAN2 |
| R3-214693 | LS on NTN specific user consent | RAN2 |
| R3-214698 | Reply LS on UE location aspects in NTN | RAN2 |
| R3-214699 | Reply LS on UE location aspects in NTN | RAN2 |
| R3-214706 | LS Response to Reply LS on UE location aspects in NTN | SA2 |
| R3-214868 | Reply LS on UE location aspects in NTN | CT1 |
| R3-214900 | Further discussion on aspects related to TAC/CGI reporting in ULI | Qualcomm Incorporated |
| R3-214901 | (TP for BL CR for 38.413) Verification of ULI | Qualcomm Incorporated |
| R3-215096 | Discussion on UE Location Aspects in NTN | Huawei |
| R3-215097 | [DRAFT] Reply LS on UE location aspects in NTN | Huawei |
| R3-215098 | [DRAFT] Reply LS on UE location aspects and Multiple TACs per PLMN | Huawei |
| R3-215102 | Location Report Trigger Conditions | Huawei |
| R3-215103 | [DRAFT] LS on location report trigger condition | Huawei |
| R3-215257 | UE Location Aspects in NTN | Ericsson LM |
| R3-215258 | [DRAFT] Reply LS on UE Location Aspects in NTN | Ericsson LM |
| R3-215349 | Discussion on indication in the ULI how the mapped cell ID was obtained | Nokia, Nokia Shanghai Bell |
| R3-215350 | (TP for BL CR for TS 38.300) Discussion on the support for multiple TAC | Nokia, Nokia Shanghai Bell |
| R3-215462 | Multi TAC handling and reporting | THALES |
| R3-215590 | Discussion on indicating TAI toward the Core Network | CATT |
| R3-215591 | [Draft] LS Response on UE location aspects in NTN | CATT |
| R3-215592 | (TP for BL CR for TS 38.300) On CGI mapping | CATT |
| R3-215767 | Discussion on UE location aspects in NTN | ZTE |
| R3-215768 | [Draft] Reply LS on UE location aspects in NTN | ZTE |
| R3-215881 | CB: # 2002_NTN_NW-ID - Summary of email discussion | Qualcomm - moderator |
| R3-216015 | Reply LS on UE Location Aspects in NTN | Ericsson LM |
| R3-216067 | Reply LS on UE Location Aspects in NTN | Ericsson LM |
| 20.2.3 | Cell Relation Handling | |
| R3-215101 | no support of Xn interface | Huawei |
| R3-215740 | Further Discussion on Cell Relation for NTN | ZTE |
| R3-215882 | CB: # 2003_NTN_Cell_Rel - Summary of email discussion | ZTE - moderator |
| 20.2.4 | Feeder Link Switch-Over for LEO | |
| R3-215351 | Discussion on enhancement on Xn interface for Feeder link switch over | Nokia, Nokia Shanghai Bell |
| R3-215593 | Discussion on feederlink switch | CATT |
| R3-215678 | Discussion on feeder link switch for NTN | CMCC |
| R3-215741 | Further Discussion on Feeder Link Switch-over for LEO | ZTE |
| R3-215883 | CB: # 2004_NTN_Feeder_Link - Summary of email discussion | CMCC - moderator |
| 20.2.5 | Aspects Related to Country-Specific Routing | |
| R3-214836 | Country specific routing issue | China Telecommunication |
| R3-214838 | Country specific routing issue | China Telecommunication |
| R3-214902 | (TP for BL CR for 38.300) Final aspects of country border crossing | Qualcomm Incorporated |
| R3-215594 | (TP for BL CR for TS 38.300) On country policy handling | CATT |
| R3-215742 | Further Discussion on Country-specific Routing for NTN | ZTE |
| R3-215884 | CB: # 2005_NTN_Country_Routing - Summary of email discussion | CATT - moderator |
| R3-216039 | (TP for BL CR for TS 38.300) On country policy handling | CATT |
| R3-216092 | CB: # 2005_NTN_Country_Routing - Summary of email discussion | CATT - moderator |
| R3-216093 | (TP for BL CR for TS 38.300) On country policy handling | CATT |
| 21.1 | General | |
| R3-214625 | Introduction of Enhanced IIoT support over NG | CATT, Nokia, Nokia Shanghai Bell, Samsung, Huawei, Ericsson, ZTE |
| R3-214626 | Introduction of Enhanced IIoT support over E1 | ZTE, Nokia, Nokia Shanghai Bell, Samsung, CATT, Huawei, Ericsson |
| R3-214627 | Introduction of Enhanced IIoT support over F1 | Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE, Samsung |
| R3-214657 | Introduction of Enhanced IIoT support over Xn | Ericsson, Samsung, Huawei, ZTE,CATT, Nokia, Nokia Shanghai Bell |
| R3-216263 | Introduction of Enhanced IIoT support over NG | CATT, Nokia, Nokia Shanghai Bell, Samsung, Huawei, Ericsson, ZTE |
| R3-216264 | Introduction of Enhanced IIoT support over Xn | Ericsson, Samsung, Huawei, ZTE,CATT, Nokia, Nokia Shanghai Bell |
| R3-216265 | Introduction of Enhanced IIoT support over E1 | ZTE, Nokia, Nokia Shanghai Bell, Samsung, CATT, Huawei, Ericsson |
| R3-216266 | Introduction of Enhanced IIoT support over F1 | Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE, Samsung |
| 21.2 | Support for Propagation Delay Compensation Enhancements | |
| R3-214735 | (TP for Introduction of Enhanced IIoT support over NG and Xn) Further discussion on Time Synchronization enhancements | ZTE |
| R3-214736 | (TP for Introduction of Enhanced IIoT support over F1)Time Synchronization enhancements | ZTE |
| R3-214828 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.413) Time synchronisation assistance information | Nokia, Nokia Shanghai Bell |
| R3-214829 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.423) Impact of handover on time synchronization | Nokia, Nokia Shanghai Bell |
| R3-214903 | (TP for BL CR for 38.413 IIOT) AS Time Distribution | Qualcomm Incorporated |
| R3-215081 | Discussion on supporting the gNB-based Packet Delay Compensation | Samsung |
| R3-215082 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.413) Discussion on supporting the time synchronization error budget | Samsung |
| R3-215122 | TP for BLCR for 38.413 on Propagation Delay Compensation Enhancements | CATT |
| R3-215131 | (TP for eIIOT BLCR for TS 38.413) Supporting propagation delay compensation enhancements | Huawei |
| R3-215132 | (TP for eIIOT BLCR for TS 38.423) Supporting propagation delay compensation enhancements | Huawei |
| R3-215154 | Discussion on Further enhanced NR-IIoT: Enhancements for support of time synchronization | Ericsson |
| R3-215155 | Enhancements for support of time synchronization | Ericsson |
| R3-215156 | Enhancements for support of time synchronization | Ericsson |
| R3-215885 | CB: # NRIIOR1_PDC - Summary of email discussion | Nokia - moderator |
| R3-215923 | Enhancements for support of time synchronization | Ericsson |
| R3-215953 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.413) Time synchronisation assistance information | Nokia, Nokia Shanghai Bell |
| R3-215954 | (TP for eIIOT BLCR for TS 38.423) Supporting propagation delay compensation enhancements | Huawei |
| R3-215955 | (TP for Introduction of Enhanced IIoT support over F1)Time Synchronization enhancements | ZTE |
| R3-215956 | CB: # NRIIOR1_PDC - Summary of email discussion | Nokia - moderator |
| 21.3 | Enhancements Based on New QoS Related Parameters | |
| R3-214737 | (TP for Introduction of Enhanced IIoT support over NG/Xn/F1/E1) Analysis of New QoS Related parameters | ZTE |
| R3-214830 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.423) Survival Time and handover | Nokia, Nokia Shanghai Bell |
| R3-215083 | Discussion on the remaining issues for the Survival Time | Samsung |
| R3-215123 | Discussion on new QoS related parameters | CATT |
| R3-215124 | (TP for BLCR for TS 38413) new QoS related parameters | CATT |
| R3-215133 | (TP for eIIOT BLCR for TS 38.473) Survival time remaining issues | Huawei |
| R3-215886 | CB: # NRIIOT2_NewQoS - Summary of email discussion | ZTE - moderator |
| R3-215957 | CB: # NRIIOT2_NewQoS - Summary of email discussion | ZTE - moderator |
| R3-215978 | (TP for BLCR for TS 38413) new QoS related parameters | CATT |
| R3-215979 | (TP for NR_IIOT_URLLC_enh BL CR for TS 38.423) Survival Time and handover | Nokia, Nokia Shanghai Bell |
| R3-215980 | (TP for eIIOT BLCR for TS 38.473) Survival time remaining issues | Huawei |
| R3-215981 | (TP for eIIOT BLCR for TS 38.463) Survival time remaining issues | ZTE |
| 22.1 | General | |
| R3-214604 | Introduction of MBS(BL CR for 38.463) | CATT |
| R3-214605 | Introduction of NR MBS | Lenovo, Motorola mobility |
| R3-214611 | Introduction of NR MBS | Samsung |
| R3-214613 | Introduction of NR MBS | LG Electronics |
| R3-214658 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-214659 | Introduction of NR MBS | Huawei, CMCC |
| R3-214660 | MBS BL CR for TS38.410 | ZTE |
| R3-214661 | BL CR for NR MBS for 38.413 | Qualcomm |
| R3-214662 | Introduction of NR Multicast and Broadcast Services | Ericsson |
| R3-214666 | BL CR to TS38.420 | CMCC |
| R3-216267 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-216268 | MBS BL CR for TS38.410 | ZTE |
| 22.2.2 | Session Management over NG | |
| R3-214788 | (TP for 38.413) Stage 3 for MBS Context and UE MBS Context | Nokia, Nokia Shanghai Bell |
| R3-214789 | (TP for 38.413) Stage 3 for User Plane Shared Delivery Tunnel | Nokia, Nokia Shanghai Bell |
| R3-214790 | (TP for 38.413) Stage 3 for Broadcast Session | Nokia, Nokia Shanghai Bell, Huawei |
| R3-215059 | TP for 38.413 on session management for broadcast | CATT |
| R3-215060 | TP to 38.410 on session management for multicast | CATT |
| R3-215138 | Consideration on Multicast Session Management | Huawei, CBN, Lenovo, Motorola Mobility, Qualcomm Incorporated, China Unicom, China Telecom |
| R3-215139 | (TP to TS 38.410 BL CR) Multicast Session Management | Huawei, CBN, Lenovo, Motorola Mobility, Qualcomm Incorporated, China Unicom, China Telecom |
| R3-215140 | (TP to TS 38.413 BL CR) Multicast Session Management | Huawei, CBN, Lenovo, Motorola Mobility, Qualcomm Incorporated, China Unicom, China Telecom, CMCC |
| R3-215202 | Reflections on Session Management for multicast NR MBS | Ericsson |
| R3-215203 | [TP for BL CR 38.300, 38.401, 38.410] on Session Management for NR MBS | Ericsson |
| R3-215204 | [TP for BL CR 38.413, 38.423] on Session Management for NR MBS | Ericsson |
| R3-215240 | (TP to TS 38.470 BL CR) Multicast Session Management | Qualcomm Incorporated, Huawei, Lenovo, Motorola Mobility |
| R3-215241 | (TP to TS 38.473 BL CR) Multicast Session Management | Qualcomm Incorporated, Huawei, Lenovo, Motorola Mobility |
| R3-215515 | MBS Session management for broadcast and multicast | Samsung |
| R3-215620 | (TP for TS 38.413) Management of multicast session | ZTE Corporation |
| R3-215621 | (TP for TS 38.300) Management of multicast session | ZTE Corporation |
| R3-215622 | (TP for TS 38.410) Management of multicast session | ZTE Corporation |
| R3-215677 | MBS Session management over NG for multicast | CMCC |
| R3-215697 | (TP to TS 38.300) MBS session management over NG | CMCC, Huawei |
| R3-215887 | CB: # MBS1_SessMgmt - Summary of email discussion | Huawei - moderator |
| R3-215985 | CB: # MBS1_SessMgmt - Summary of email discussion | Huawei - moderator |
| R3-216046 | (TP to TS 38.410 BL CR) Multicast Session Management | Huawei, CBN, Lenovo, Motorola Mobility, Qualcomm Incorporated, China Unicom, China Telecom |
| 22.2.3 | Dynamic Change Between PTP and PTM for UEs in RRC_CONNECTED State | |
| R3-214791 | (TP for 38.401) Stage 2 for PTP-PTM switch | Nokia, Nokia Shanghai Bell |
| 22.2.4 | Bearer Management over F1/E1 | |
| R3-215043 | Further Consideration on MBS Bearer Management over F1E1 | CATT |
| R3-215044 | Further Consideration on Flow Control Mechanism over F1-U | CATT |
| R3-215046 | TP for 38.463 on MBS Bearer Management at E1 interface | CATT |
| R3-215141 | (TPs to TS 38.401 38.470, 38.460 BL CRs) Bearer management for Broadcast | Huawei, CBN, Nokia, Nokia Shanghai Bell, China Unicom, China Telecom, CMCC |
| R3-215142 | (TPs to TS 38.401, 470, 460 BL CRs) Bearer Management for Multicast | Huawei, CBN, China Unicom, China Telecom, CMCC |
| R3-215143 | (TP to TS 38.425 BL CR) Flow Control for MBS | Huawei, CBN, China Unicom, China Telecom |
| R3-215205 | On Bearer Management over E1/F1 | Ericsson |
| R3-215206 | [TP for BL CR 38.473, 38.463] On Bearer Management over E1/F1 | Ericsson |
| R3-215272 | (TP to TS 38.460 BL CR) Support of Multicast Distribution Setup and Release | Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated |
| R3-215273 | (TP to TS 38.463 BL CR) Support of Multicast Distribution Setup and Release | Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated |
| R3-215274 | Remaining Issues on F1 Interface for MBS | Lenovo, Motorola Mobility |
| R3-215372 | (TP to TS 38.425 BL CR) FLow Control over F1 for NR MBS | ZTE |
| R3-215373 | (TP to TS 38.473 BL CR) Bearer Management over F1 for NR MBS | ZTE |
| R3-215516 | Flow control for MBS multicast session | Samsung |
| R3-215673 | Discussion on MBS Bearer Management | CMCC |
| R3-215888 | CB: # MBS2_BearerMgmt - Summary of email discussion | Ericsson - moderator |
| R3-215986 | CB: # MBS2_BearerMgmt - Summary of email discussion | Ericsson - moderator |
| 22.2.5 | Others | |
| R3-215144 | (TPs to TS 38.413 TS 38.423 BL CRs) Support of Local MBS | Huawei, CBN, China Unicom |
| R3-215275 | Remaining Issues on MBS Service Area Management | Lenovo, Motorola Mobility |
| R3-215889 | CB: # MBS3_others - Summary of email discussion | Lenovo - moderator |
| R3-215987 | CB: # MBS3_others - Summary of email discussion | Lenovo - moderator |
| 22.3.1 | Mobility Between MBS Supporting Nodes | |
| R3-214792 | (TP for 38.415) Seamless Mobility between two MBS Supporting Nodes and use of data forwarding | Nokia, Nokia Shanghai Bell |
| R3-215057 | Supporting lossless handover while retaining flexible MRB mapping | CATT |
| R3-215145 | Way Forward on Mobility between MBS supporting nodes | Huawei, Qualcomm Incorporated, CMCC, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, CBN, China Telecom, CATT, LG Electronics, Samsung, China Unicom, BT, vivo, OPPO |
| R3-215146 | (TPs to TS 38.300 T38.401 BL CRs) Mobility between MBS supporting nodes | Huawei, CBN, China Unicom, China Telecom |
| R3-215147 | (TP to TS38.300 BL CR) Consideration on DL PDCP Synchronization | Huawei, CBN, China Unicom, China Telecom |
| R3-215148 | (TP to TS 38.415 BL CR) Support of NR MBS data transmission | Huawei, CBN, China Unicom, China Telecom |
| R3-215207 | On open topics for mobility between gNBs supporting NR MBS | Ericsson |
| R3-215208 | [TP for BL CR 38.463, 38.413] to support mobility between gNBs supporting NR MBS | Ericsson |
| R3-215242 | Solution analysis for mobility between supporting nodes | Qualcomm Incorporated, Huawei |
| R3-215243 | Data forwarding in handover with MBS multicast | Qualcomm Incorporated |
| R3-215277 | Enhancements to support loss-less handover for NR multicast | Lenovo, Motorola Mobility |
| R3-215374 | Analysis to PDCP SN Sync | ZTE |
| R3-215375 | LS on PDCP SN Sync to support lossless HO | ZTE |
| R3-215376 | (TP to TS 38.300 BL CR) Mobility procedure between MBS supporting nodes | ZTE |
| R3-215674 | Discussion on Mobility with Service Continuity | CMCC |
| R3-215675 | Discussion on PDCP Synchronization | CMCC |
| R3-215890 | CB: # MBS4_MobilitySupport - Summary of email discussion | ZTE - moderator |
| R3-215988 | CB: # MBS4_MobilitySupport - Summary of email discussion | ZTE - moderator |
| 22.3.2 | Mobility Between MBS Supporting and non-MBS Supporting Nodes | |
| R3-214793 | (TP for 38.300) Duplication avoidance for mobility from non-MBS supporting NG-RAN nodes | Nokia, Nokia Shanghai Bell |
| R3-215149 | (TP to TS 38.300 BL CR) Mobility between MBS supporting and non-supporting nodes | Huawei, CBN, China Unicom, China Telecom |
| R3-215278 | Service Continuity for handover from MBS Supporting Node to MBS non-Supporting Node | Lenovo, Motorola Mobility |
| R3-215676 | Discussion on Mobility between non-MBS supporting node and MBS supporting node | CMCC |
| R3-215786 | Discussion on PDCP synchronization for lossless MBS mobility to a supporting and non-supporting node | TCL Communication Ltd. |
| R3-215799 | LS on MBS data forwarding | SA2 |
| R3-215871 | Discussion on PDCP synchronization for lossless MBS mobility to a supporting or non-supporting node | TCL Communication Ltd. |
| R3-215891 | CB: # MBS5_MobilityNonSupporting - Summary of email discussion | Nokia - moderator |
| R3-215970 | LS on Feedback on data forwarding solutions for MBS | Nokia, Nokia Shanghai Bell |
| R3-215989 | CB: # MBS5_MobilityNonSupporting - Summary of email discussion | Nokia - moderator |
| R3-216185 | LS on handover from MBS supporting node to MBS non-supporting node | Lenovo |
| R3-216190 | CB: # MBS5_MobilityNonSupporting - Summary of email discussion | Nokia - moderator |
| R3-216195 | LS on Feedback on data forwarding solutions for MBS | Nokia, Nokia Shanghai Bell |
| R3-216222 | LS on handover from MBS supporting node to MBS non-supporting node | Lenovo |
| 22.4 | Others | |
| R3-214751 | (TP for 38.300 for Introduction of NR MBS) MBS broadcast service continuity | ZTE |
| R3-214794 | (TP for 38.300) Stage 2 for Broadcast Service Continuity | Nokia, Nokia Shanghai Bell |
| R3-215045 | MBS reception of Idle and In-active Ues | CATT |
| R3-215150 | (TP to TS 38.300 BL CR) Broadcast service continuity | Huawei, CBN, China Unicom, China Telecom |
| R3-215209 | On MBS SAI handling on NG-RAN internal interfaces | Ericsson |
| R3-215892 | CB: # MBS6_BroadcastService - Summary of email discussion | CATT - moderator |
| R3-215971 | (TP to TS 38.423 BL CR) Broadcast service continuity | CATT |
| R3-215990 | CB: # MBS6_BroadcastService - Summary of email discussion | CATT - moderator |
| R3-216044 | (TP for 38.300 for Introduction of NR MBS) MBS broadcast service continuity | ZTE |
| R3-216191 | (TP for 38.300 for Introduction of NR MBS) MBS broadcast service continuity | ZTE, Nokia, Nokia Shanghai Bell |
| 23.1 | General | |
| R3-215700 | Work planning for R17 Sidelink Relay WI | CMCC, OPPO |
| 23.2 | Specification of Relay and Remote UE authorization | |
| R3-214837 | Discussion on Relay and Remote UE authorization | China Telecommunication |
| R3-214839 | Discussion on Relay and Remote UE authorization | China Telecommunication |
| R3-214913 | Relay and Remote UE Authorization | Qualcomm Incorporated |
| R3-214962 | Support of NR ProSe authorization | Huawei |
| R3-214963 | Support of NR ProSe authorization | Huawei |
| R3-214973 | SL relay authorization | ZTE, Sanechips |
| R3-215283 | Authorization for Relay and Remote UE | Ericsson |
| R3-215284 | Introduction of service authorization for SL Relay over NG | Ericsson |
| R3-215285 | Introduction of service authorization for SL Relay over Xn | Ericsson |
| R3-215352 | Discussion on Relay and Remote UE authorization | Nokia, Nokia Shanghai Bell |
| R3-215353 | (NGAP CR) support for NR Sidelink Relay | Nokia, Nokia Shanghai Bell |
| R3-215354 | (XnAP CR) support for NR Sidelink Relay | Nokia, Nokia Shanghai Bell |
| R3-215355 | (F1AP CR) support for NR Sidelink Relay | Nokia, Nokia Shanghai Bell |
| R3-215595 | Discussion on UE authorization for NR SL Relay | CATT |
| R3-215596 | Support of 5G ProSe Authorization for NGAP | CATT |
| R3-215597 | Support of 5G ProSe Authorization for XnAP | CATT |
| R3-215701 | Consideration on authorization for SL relay | CMCC |
| R3-215912 | CB: # SLRelay1_Authorization - Summary of email discussion | CMCC - moderator |
| 23.3 | Specification of Control Plane procedures | |
| R3-214879 | Discussion on RRC Connection Management for sidelink relay | Samsung |
| R3-214880 | CR to TS38.401 on Sidelink Relay | Samsung |
| R3-214881 | Discussion on PC5/Uu link and mapping configuration for sidelink relay | Samsung |
| R3-214914 | Control Plane procedures and Adaptation layer design for U2N relays | Qualcomm Incorporated |
| R3-214964 | Support of NR ProSe authorization | Huawei |
| R3-214965 | Discussion on the support of ProSe service | Huawei |
| R3-214974 | RRC connection management of remote UE in CU/DU split scenario | ZTE, Sanechips |
| R3-214975 | F1 impacts for the PC5/Uu RLC channel and bearer mapping configuration | ZTE, Sanechips |
| R3-214976 | Discussion on the system information delivery and paging | ZTE, Sanechips |
| R3-215286 | Path Switch in NR SL Relay | Ericsson |
| R3-215598 | Discussion on RAN3 impact to support L2 SL Relaying | CATT |
| R3-215702 | Discussion on CP issue for SL relay | CMCC |
| R3-215913 | CB: # SLRelay2_ControlPlane - Summary of email discussion | Samsung - moderator |
| R3-215982 | CB: # SLRelay2_ControlPlane - Summary of email discussion | Samsung - moderator |
| 24.1 | General | |
| R3-214844 | Work plan for the INACTIVE small data WI | ZTE |
| R3-215996 | RA-SDT BLCR to TS 38.300 | ZTE |
| R3-215997 | RA-SDT BLCR to TS 38.401 | Intel Corporation |
| R3-215998 | RA-SDT BLCR to TS 38.423 | Ericsson |
| R3-215999 | RA-SDT BLCR to TS 38.473 | Nokia |
| R3-216000 | RA-SDT BLCR to TS 38.463 | China Telecommunication |
| R3-216059 | CG-SDT BLCR to TS 38.401 | Huawei |
| R3-216060 | CG-SDT BLCR to TS 38.473 | Samsung |
| R3-216274 | RA-SDT BLCR to TS 38.300 | ZTE |
| R3-216275 | RA-SDT BLCR to TS 38.401 | Intel Corporation |
| R3-216276 | RA-SDT BLCR to TS 38.423 | Ericsson |
| R3-216277 | RA-SDT BLCR to TS 38.473 | Nokia, Nokia Shanghai Bell |
| 24.2 | Support of Context Fetch and Data Forwarding | |
| R3-214845 | Discussion on RACH based SDT | ZTE |
| R3-214847 | BLCR 38.300 for support of SDT | ZTE |
| R3-214883 | Discussion on RA-based small data transmission | Samsung |
| R3-214904 | Further discussion on RAN3 impacts of RACH based SDT | Qualcomm Incorporated |
| R3-215000 | (TPs to TS 38.300 38.473 38.401BL CRs) Support of RACH based SDT | Huawei |
| R3-215001 | Supporting of RACH based SDT | Huawei |
| R3-215279 | Context fetch and data forwarding for NR SDT | Ericsson |
| R3-215280 | Support of NR SDT over Xn | Ericsson |
| R3-215319 | SDT Related Procedures | Lenovo, Motorola Mobility |
| R3-215356 | Support of RACH-based SDT | Nokia, Nokia Shanghai Bell |
| R3-215368 | Support of RACH-based SDT | Nokia, Nokia Shanghai Bell |
| R3-215599 | Discussion on RA-based SDT with anchor relocation | CATT |
| R3-215600 | Discussion on RA-based SDT without anchor relocation | CATT |
| R3-215601 | Support of RA-based SDT | CATT |
| R3-215709 | Consideration on small data transmission without anchor relocation | LG Electronics |
| R3-215710 | Support of RACH-based SDT over Xn | LG Electronics |
| R3-215745 | Context retrieval and data forwarding for RACH based SDT | Intel Corporation |
| R3-215746 | Assistance Information from New gNB for RACH based SDT | Intel Corporation |
| R3-215747 | [Draft] SDT BL CR to 38.423 | Intel Corporation |
| R3-215893 | CB: # SDT1_RACHbased - Summary of email discussion | ZTE - moderator |
| R3-216012 | CB: # SDT1_RACHbased - Summary of email discussion | ZTE - moderator |
| R3-216022 | CB: # SDT1_RACHbased - Summary of email discussion | ZTE - moderator |
| R3-216069 | (TP for RA-SDT BLCR to TS 38.473) Support of RA-based SDT | Qualcomm |
| R3-216070 | (TP for RA-SDT BLCR to TS 38.300) Support of RA-based SDT | CATT |
| R3-216071 | (TP for RA-SDT BLCR to TS 38.401) Support of RA-based SDT | Huawei |
| R3-216081 | (TP for RA-SDT BLCR to TS 38.423) Support of RA-based SDT | Nokia, Nokia Shanghai Bell |
| R3-216229 | CB: # SDT1_RACHbased - Summary of email discussion | ZTE - moderator |
| 24.3 | Support of CG based SDT | |
| R3-214846 | Discussion on CG based SDT | ZTE |
| R3-214848 | BLCR 38.401 for support of SDT | ZTE |
| R3-214882 | CR to F1AP on Rel-17 SDT | Samsung |
| R3-215002 | (TP to TS 38.473 BL CR) Support of CG based SDT | Huawei |
| R3-215003 | Support of NR Small Data Transmissions in INACTIVE state | Huawei |
| R3-215281 | F1 impacts by supporting CG-based SDT | Ericsson |
| R3-215282 | Support of NR SDT over F1 | Ericsson |
| R3-215320 | Support of CG-SDT | Lenovo, Motorola Mobility |
| R3-215369 | Support of CG-based SDT | Nokia, Nokia Shanghai Bell |
| R3-215370 | Support of CG-based SDT | Nokia, Nokia Shanghai Bell |
| R3-215394 | Discussion on CG-based small data transmission | Samsung |
| R3-215602 | Discussion on CG based SDT in CU-DU split architecture | CATT |
| R3-215672 | Discussion of E1 impact on CG-based SDT | China Telecom |
| R3-215711 | Discussion on CG-based SDT in CU-DU split | LG Electronics |
| R3-215712 | Support of CG-SDT in CU-DU split | LG Electronics |
| R3-215748 | CG based SDT impact on CU-DU split | Intel Corporation |
| R3-215750 | CR to 38.463 on support of SDT in E1 interface | China Telecomunication Corp. |
| R3-215894 | CB: # SDT2_CGbased - Summary of email discussion | LG Electronics - moderator |
| R3-216023 | CB: # SDT2_CGbased - Summary of email discussion | LG Electronics - moderator |
| 24.4 | Others | |
| R3-214884 | Discussion on other issues related to SDT | Samsung |
| R3-215321 | DL non-SDT data and signalling arrival during SDT procedure | Lenovo, Motorola Mobility |
| R3-215895 | CB: # SDT3_others - Summary of email discussion | Samsung - moderator |
| R3-216024 | CB: # SDT3_others - Summary of email discussion | Samsung - moderator |
| 30.1 | NB-IoT and eMTC support for NTN | |
| R3-214696 | LS on supporting discontinuous coverage in IoT NTN | RAN2 |
| R3-215743 | Initial Consideration on NB-IoT and eMTC Support for NTN | ZTE |
| R3-215803 | Reply LS on EPS support for IoT NTN in Rel-17 | SA2 |
| 30.4 | Others | |
| R3-214623 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-214632 | CR to 38.425: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson |
| R3-214636 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-214637 | Further discussions on logical entities and corresponding definitions | Huawei, Ericsson |
| R3-214638 | CR to 38.462 on the introduction of new interface | Huawei, Ericsson |
| R3-214639 | CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB | Huawei, Ericsson |
| R3-215089 | Correction on enhanced eNB architecture evolution | Huawei, Telecom Italia |
| R3-215090 | Use of node ID in eNB | Huawei, Telecom Italia |
| R3-215493 | (TP for Enh-eNB Arch Evol BL CR for TS 38.460) LTE CP-UP split leftovers | Ericsson |
| R3-215494 | (TP for Enh-eNB Arch Evol BL CR for TS 38.425) Reconsidering restrictions for eNBs | Ericsson |
| R3-215782 | (TP for BL CR TS 38.401) Correction on enhanced eNB architecture evolution | Huawei, Telecom Italia |
| R3-215783 | (TP for BL CR TS 38.401) Use of node ID in eNB | Huawei, Telecom Italia |
| R3-215896 | CB: # 61_eNBarchEvo - Summary of email discussion | China Unicom - moderator |
| R3-216074 | (TP for BL CR TS 38.401) Use of node ID in eNB | Huawei, Telecom Italia |
| R3-216240 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-216241 | Further discussions on logical entities and corresponding definitions | Huawei, Ericsson |
| 31.1.1 | Inclusive Language Review | |
| R3-214680 | Reply LS on Inclusive language for ANR | RAN2 |
| R3-214700 | LS on Inclusive Language Review Status and Consistency Check | RAN4 |
| R3-214831 | Inclusive language review for TS 25.467 | Nokia, Nokia Shanghai Bell |
| R3-215835 | CB: # 32_InclusiveLanguage - Summary of email discussion | Ericsson - moderator |
| 31.1.2 | Rapporteur Review | |
| R3-214832 | NGAP rapporteur corrections | Nokia, Nokia Shanghai Bell |
| R3-214945 | Rapporteur Update of 38.401 | NEC |
| R3-214966 | Editorial updates | Huawei |
| R3-215210 | XnAP Rapporteur Corrections | Ericsson |
| R3-215287 | X2AP Rapporteur Corrections | Ericsson |
| R3-215421 | NRPPa Rapporteur Corrections | Ericsson |
| R3-215492 | E1AP Rapporteur Corrections | Ericsson |
| R3-215540 | Rapporteur Corrections to TS38.425 | Samsung |
| R3-215836 | CB: # 33_RapporteurUpdates - Summary of email discussion | NEC - moderator |
| 31.2.1 | Local NG-RAN Node Identifier | |
| R3-214740 | Discussion on I-RNTI partitioning | ZTE, Radisys, Reliance JIO, China Telecom |
| R3-214741 | Support flexible I-RNTI partitioning | ZTE, Radisys, Reliance JIO, China Telecom |
| R3-214742 | Support flexible I-RNTI partitioning | ZTE, Radisys, Reliance JIO, China Telecom |
| R3-214763 | Node Identifier for RRC Inactive | Ericsson |
| R3-214764 | Addition of Local gNB IDs per NG-RAN node [RRCInactive] | Ericsson |
| R3-214820 | Down-Selection of Local NG-RAN node Identifier solutions | Nokia, Nokia Shanghai Bell |
| R3-214821 | Support of Local NG-RAN node Identifier [Local_Node_ID] | Nokia, Nokia Shanghai Bell |
| R3-215030 | Discussion on Local NG-RAN Node Identifier | Huawei |
| R3-215031 | Local NG-RAN Node Identifier | Huawei |
| R3-215837 | CB: # 34_LocalNG-RANnode_Identifier - Summary of email discussion | Ericsson - moderator |
| R3-216076 | Support flexible I-RNTI partitioning [RRCInactive] | ZTE, Radisys, Reliance JIO, China Telecom, Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-216079 | Introduction of Local NG-RAN Node IDs for RRC_INACTIVE [RRCInactive] | Ericsson, ZTE, Radisys, Reliance JIO, China Telecom, Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-216187 | Support flexible I-RNTI partitioning [RRCInactive] | ZTE, Radisys, Reliance JIO, China Telecom, Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Huawei |
| R3-216208 | CB: # 34_LocalNG-RANnode_Identifier - Summary of email discussion | Ericsson - moderator |
| 31.2.2 | PDCP Duplication | |
| R3-214849 | Correction on UL PDCP duplication | ZTE |
| R3-215125 | Discussion on UL PDCP Duplication | CATT |
| R3-215126 | CR to 38.425 for handling of UL PDCP Duplication status information | CATT |
| R3-215136 | Assistance information for UL duplication | Huawei, China Unicom, China Telecom, CATT |
| R3-215137 | Assistance information for UL duplication [UL_duplication] | Huawei, China Unicom, China Telecom, CATT |
| R3-215179 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-215180 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-215181 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-215183 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-215838 | CB: # 35_PDCPDuplication - Summary of email discussion | Huawei - moderator |
| R3-215924 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| R3-215925 | Handling PDCP Duplication | Ericsson, Intel Corporation, Nokia, Nokia Shanghai Bell |
| 31.2.3 | PRACH Coordination Between LTE and NR | |
| R3-215032 | PRACH Coordination Between LTE and NR | Huawei |
| R3-215033 | PRACH Coordination Between LTE and NR | Huawei |
| R3-215034 | PRACH Coordination Between LTE and NR | Huawei |
| R3-215227 | Analysis of PRACH Coordination Between LTE and NR | Ericsson |
| R3-215261 | PRACH Coordination Between LTE and NR | Huawei |
| R3-215262 | PRACH Coordination Between LTE and NR | Huawei |
| R3-215671 | Potential Solutions for PRACH Coordination between LTE and NR | China Telecom |
| R3-215761 | Consideration on Resource Coordination between LTE and NR | ZTE |
| R3-215762 | (TP for SON BL CR for TS 36.413) Introduce Resource Coordination between LTE and NR | ZTE |
| R3-215763 | (TP for SON BL CR for TS 38.413) Introduce Resource Coordination between LTE and NR | ZTE |
| R3-215839 | CB: # 36_PRACHCoordination - Summary of email discussion | China Telecom - moderator |
| 31.2.4 | Rx-Tx Measurement Reporting | |
| R3-215263 | Addition of NR Timing Advance reporting for NR UL E-CID [NRTADV] | Ericsson, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, CATT, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-215264 | Addition of NR Timing Advance reporting for NR UL E-CID [NRTADV-F1] | Ericsson, CATT, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, Nokia, Nokia Shanghai Bell, Huawei |
| R3-215267 | Addition of NR Timing Advance reporting for NR UL E-CID [NRTADV-F1] | Ericsson, CATT, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-215787 | LS on NR Positioning support for TA measurement in NR UL E-CID | RAN1 |
| R3-215840 | CB: # 37_RxTxMeasureReport - Summary of email discussion | Ericsson - moderator |
| R3-216063 | Addition of NR Timing Advance reporting for NR UL E-CID [NRTADV-F1] | Ericsson, CATT, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-216065 | Addition of NR Timing Advance reporting for NR UL E-CID [NRTADV] | Ericsson, NTT Docomo, Polaris Wireless, Verizon, China Telecom, FirstNet, Deutsche Telekom, Intel Corporation, CATT, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| 31.2.5 | Support exchange of protocol support at target RAN node for NG handover | |
| R3-215211 | Support exchange of protocol support at target RAN node for NG handover | Ericsson |
| R3-215212 | Support exchange of protocol support at target RAN node for NG handover | Ericsson |
| R3-215213 | Support exchange of protocol support at target RAN node for NG handover | Ericsson |
| R3-215247 | Further discussion on RACS Capability Detection for S1 and NG handover | Qualcomm Incorporated, Vodafone |
| R3-215248 | Detection of RACS support at target during N2/S1 handover | Qualcomm Incorporated, Vodafone |
| R3-215249 | Detection of RACS support at target during N2/S1 handover | Qualcomm Incorporated, Vodafone |
| R3-215357 | On node capability detection for non-direct-connected nodes | Huawei, China Unicom, China Telecom |
| R3-215358 | On node capability detection for non-direct-connected nodes [Node_Cap_Dect] | Huawei, China Unicom, China Telecom |
| R3-215359 | On node capability detection for non-direct-connected nodes [Node_Cap_Dect] | Huawei, China Unicom, China Telecom |
| R3-215841 | CB: # 38_ProtocolSupport - Summary of email discussion | Qualcomm - moderator |
| 31.2.6 | Others | |
| R3-214801 | Path status indication for EN-DC | Nokia, Nokia Shanghai Bell |
| R3-214802 | Path status information | Nokia, Nokia Shanghai Bell |
| R3-214972 | Prioritization of S-NSSAI(s) | Nokia, Nokia Shanghai Bell, Verizon Wireless |
| R3-215035 | Discussion on CSI-RS configuration request | Huawei, China Telecom, China Unicom |
| R3-215036 | CSI-RS configuration request [CSI_RS_Req] | Huawei, China Telecom, China Unicom |
| R3-215037 | CSI-RS configuration request [CSI_RS_Req] | Huawei, China Telecom, China Unicom |
| R3-215038 | Correction on release-with-redirect in 2-step RRC resume procedure | Huawei, China Unicom, CMCC, Qualcomm Incorporated |
| R3-215039 | Correction on release-with-redirect in 2-step RRC resume procedure | Huawei, China Unicom, CMCC, Qualcomm Incorporated |
| R3-215075 | Addition of Test Flag | one2many B.V. |
| R3-215078 | Discussion on MIMO Configuration signalling over F1 | Nokia, Nokia Shanghai Bell |
| R3-215080 | PLMN Not Supported Cause Value [PLMN_CAUSE_E1] | Nokia, Nokia Shanghai Bell |
| R3-215222 | Corrections of procedures for PWS tests | Ericsson, One2many, KPN |
| R3-215223 | Addition of Test Flag for PWS | Ericsson, One2many, KPN |
| R3-215413 | Addition of the CSI-RS request from the source node | Ericsson, China Telecom, ZTE, Nokia, Nokia Shanghai Bell |
| R3-215414 | Addition of Additional Measurement Timing Configuration List Request Indicator IE [CSIRSXn-1] | Ericsson, China Telecom, ZTE |
| R3-215415 | Addition of Additional Measurement Timing Configuration List Request Indicator IE [CSIRSX2-1] | Ericsson, China Telecom, ZTE |
| R3-215482 | UL primary path signaling over E1 | Ericsson |
| R3-215842 | CB: # 39_CSI-RSConfigExchange - Summary of email discussion | Ericsson - moderator |
| R3-215845 | Secondary RAT Data Usage Report Configuration for MR-DC | RadiSys, Reliance JIO |
| R3-215846 | Discussion on Secondary RAT Data Usage Report Configuration for ENDC and MRDC | RadiSys, Reliance JIO |
| R3-215848 | Secondary RAT Data Usage Report Configuration for EN-DC | RadiSys, Reliance JIO |
| R3-215921 | Addition of Test Flag for PWS [TEI17_TestFlag] | Ericsson, One2many, KPN |
| R3-215922 | Addition of Test Flag [TEI17_TestFlag] | one2many B.V. |
| R3-215947 | CB: # 113_2step_RRCResume - Summary of email discussion | Qualcomm - moderator |
| R3-215948 | CB: # 114_PWSTest - Summary of email discussion | Ericsson - moderator |
| R3-216028 | LS on Clarifications to the Test Flag functionality | Ericsson |
| R3-216171 | Addition of Test Flag for PWS [TEI17_TestFlag] | Ericsson, One2many, KPN |
| R3-216172 | Addition of Test Flag [TEI17_TestFlag] | one2many B.V. |
| R3-216180 | CB: # 114_PWSTest - Summary of email discussion | Ericsson - moderator |
| R3-216193 | CSI-RS configuration request Indicator [CSIRSXn] | Ericsson, China telecom, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-216194 | CSI-RS configuration request Indicator [CSIRSX2] | Ericsson, China telecom, Huawei, ZTE, Nokia, Nokia Shanghai Bell |